Breadcrumb(); > Message Index (by Number) (by Subsystem) > Application Poller Subsystem Messages
![]()
Application Poller Subsystem Messages
The Application Poller1.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.management.deploy.internal Localization package.
Info: Activating application: appName
Description
Activate started for the application. Cause
This is an informational message only. Action
No action required. Info: Removing application: appName
Description
Remove started for the application. Cause
This is an informational message only. Action
No action required. Error: An exception occurred while auto-deploying application: appName.
Description
Deployment for the application failed. Cause
Deployment of an application can fail for many reasons. Refer to 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. Error: An exception occurred while deploying an application appName: th.
Description
Activate for the application failed. Cause
Deployment of an application can fail for many reasons. 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 application. 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 propagated to the managed servers. To propagate your changes to the managed servers, 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 propagated to the managed servers. To propagate your changes to managed servers, redeploy the application by touching the REDEPLOY file. Cause
This is a warning message only. Action
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 located in META-INF/REDEPLOY. Notice: description - status
Description
Deployment status. Cause
This is informational message only. Action
No action required. Error: The directory for autodeployed applications: 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 may be an error on the local File System of the Admin Server. Action
Correct the error by creating the directory or making sure read/write permissions exist. Critical: The DeployerRuntime MBean lookup failed. msg
Description
This may affect Auto Deployment in Development mode. Cause
The Deployment subsystem did not initialize correctly. Action
This error should not occur. Report this problem to BEA support. 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. 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. Error: Runtime deployment error while deploying - th.
Description
This message indicates an unforeseen runtime error during deployment. Cause
Unknown. Action
Please refer to the runtime error in the message. Error: 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. Info: Application "appName" is being redeployed, because it changed since the previous server run.
Description
Application "appName" is being redeployed, because it changed since the previous server run. Cause
This application is deployed using auto-deployment. The application was modified while the server was down. Hence it will be redeployed by the auto-deployment poller. Another possible reason is that the internal file used by the poller was removed or moved from disk. In that case, it assumes applications have changed. Action
No action is required. This is an informational message to explain why this deployment was redeployed after its deployment at startup. Error: appName not deployed. Auto Deploy is not currently supported in beantree mode.
Description
temp msg Cause
temp msg Action
temp msg Warning: Couldnot create directory for autodeployed applications: msg
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 may be an error on the local File System of the Admin Server. Action
Correct the error by creating the directory or making sure read/write permissions exist. Error: exception encountered while migrating app poller applications ioe.
Description
Exception occurred while modifying applications path. Cause
Exception occurred while modifying applications path. Action
Please report to support. Notice: Application migrated appName - newPath
Description
Application migrated appName - newPath Cause
This is informational message only. Action
No action required. Warning: Another process is using this file 'f'. The server will attempt to deploy the application once it is unlocked by the other process.
Description
Another process is using this file 'f'. The server will attempt to deploy the application once it is unlocked by the other process. Cause
Some other process has a lock on the file that is in the hot deploy directory. The application could still be in the process of being copied. Action
Ensure no other process is attempting to lock part or all of this application file. If the copy is ongoing, then no action should be necessary.
![]()