The Application Poller 1.0
catalog contains messages in the range
BEA149400 - BEA149449.
Messages in this catalog are part of the
weblogic.management.deploy.internal
Internationalization package and the
weblogic.i18n
Localization package.
BEA-149400
|
Info: Activating application: appName
Description
| Activate started for the application. |
Cause
| This is an informational message only. |
Action
| No action required. |
|
BEA-149401
|
Info: Removing application: appName
Description
| Remove started for the application. |
Cause
| This is an informational message only. |
Action
| No action required. |
|
BEA-149402 (retired)
|
Error: An exception occurred while auto-deploying application: appName.
Description
| Deployment for the application failed. |
Cause
| Deployment of an applicaton can fail for many reasons. Please see the exception. |
Action
| Review the exception. To redeploy the application after correcting the error condition, touch the file called REDEPLOY in the META-INF or WEB-INF directory of the exploded application. |
|
BEA-149408
|
Error: An exception occurred while deploying an application appName: th.
Description
| Activate for the application failed. |
Cause
| Deployment of an applicaton can fail for many reasons. Please refer to the exception details. |
Action
| Review the exception. To redeploy the application after correcting the error condition, touch the file called REDEPLOY in the META-INF or WEB-INF directory of the exploded applicatoin. |
|
BEA-149403
|
Warning: Warning: Application appName deployed from the applications directory has components that are deployed on servers other than the admin server. Refresh of static content (such as JSPs and HTML pages) will not be automatically propogated to the managed servers. To propogate your changes to the managed servers, you must redeploy the application by touching the REDEPLOY file.
Description
| An application deployed from the applications directory has components that are deployed on servers other than the admin server. Refresh of static content (such as JSPs and HTML pages) will not be automatically propogated to the managed servers. To propogate your changes to managed servers, you must redeploy the application by touching the REDEPLOY file. |
Cause
| This is a warning message only. |
Action
| Please touch the REDEPLOY file to properly redeploy the application. The REDEPLOY file is located in the same directory as the deployment descriptor. For EAR files, it is in META-INF/REDEPLOY. |
|
BEA-149404 (retired)
|
Notice:
Description
| Deployment status. |
Cause
| This is informational message only. |
Action
| No action required. |
|
BEA-149405
|
Error: The starting directory for the ApplicationPoller: msg could not be found.
Description
| This message is reported on server startup when the ApplicationPoller is initializing. This may impact the Autodeployment feature available in Development Mode. |
Cause
| This maybe an error on the local FileSystem of the Admin Server. |
Action
| Correct the error by creating the directory or making sure read/write permissions exist. |
|
BEA-149406 (retired)
|
Critical: The DeployerRuntime MBean lookup failed. msg
Description
| This may affect AutoDeployment in Development mode. |
Cause
| The Deployment subsystem did not initialize correctly. |
Action
| You should not be seeing this error. Report this problem to BEA support. |
|
BEA-149407
|
Error: An error occurred while undeploying application appName : t.
Description
| Undeployment of the application failed. |
Cause
| Undeployment can fail for many reasons. |
Action
| Review the error message and take corrective action. |
|
BEA-149409
|
Error: Caught exception while starting the applications poller on server start th.
Description
| The application poller did not run successfully when the server was starting. |
Cause
| Some misconfigured application may be present in the applications directory. |
Action
| Review the exception message in the server log. |
|
BEA-149410
|
Critical: Uncaught exception while polling the applications directory th. Autodeployment thread will exit.
Description
| This exception was not handled in the deployment. This causes the poller thread to exit. |
Cause
| An internal server error may have caused this. |
Action
| Report the problem to BEA support. |
|
BEA-149411
|
Debug: I/O Exception encountered ioe.
Description
| An I/O exception denotes a failure to perform a read/write operation on the application files. |
Cause
| An I/O exception can occur during file read/write while deploying an application. |
Action
| Take corrective action based on the exception message details. |
|