|
BEA-149200(retired)
|
Error: Unable to interpret the change request.
|
Description
| The targeted server received a list of changes that were not of type OamDelta and cannot be interpreted.
|
|
Cause
| This is most likely due to a classloader problem or mismatched server types.
|
|
Action
| The server is not managing deployments properly. Shut it down and refer to the documentation regarding the compatibility of various server versions.
|
|
|
BEA-149201(retired)
|
Error: Failed to complete the deployment task with ID task for the application 'application'.
|
Description
| The targeted server was unable to initiate the task specified. If the specified target is a cluster and this server is a managed server in that cluster, the entire deployment will be rolled back.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level and reinitiate the deployment request.
|
|
|
BEA-149202
|
Error: Encountered an exception while attempting to commit the task task for the application 'application'.
|
Description
| The targeted server was unable to commit the task specified. This is an internal error that should not ever occur and reflects a serious problem with the configuration of the server.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149203(retired)
|
Error: Encountered an exception while attempting to rollback the task task for the application 'application'.
|
Description
| The targeted server was unable to rollback the task specified. This is an internal error that should not ever occur and reflects a serious problem with the configuration of the server.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149204(retired)
|
Error: The deployment framework was unable to register with the Data Replication Service.
|
Description
| The Managed Server will not be able to receive updates for the application deployed on it, because it was unable to register with the Data Replication Service.
|
|
Cause
| This is likely because the managed server was unable to connect to the administration server.
|
|
Action
| Determine why the server cannot establish network connectivity with the administration server, correct the problem, and restart this managed server.
|
|
|
BEA-149205
|
Error: Failed to initialize the application 'application' due to error ex.
|
Description
| The targeted server was unable to initialize the application because the application container encountered an error.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149206(retired)
|
Error: Failed to stage the component 'application' of the application 'uri'. Underlying error is 'originalMsg'
|
Description
| The targeted server was unable to ensure that the component was available for loading by the local server. Underlying error is 'originalMsg'.
|
|
Cause
| This is likely because the managed server was unable to connect to the administration server.
|
|
Action
| Determine why the server cannot establish network connectivity with the administration server, correct the problem, and restart this managed server.
|
|
|
BEA-149207(retired)
|
Info: Initializing.
|
Description
| The Slave Deployer is initializing.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149208(retired)
|
Info: Initialization Complete.
|
Description
| The Slave Deployer is initialized.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149209
|
Info: Resuming.
|
Description
| The Slave Deployer is resuming.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149210(retired)
|
Info: Resumed.
|
Description
| The Slave Deployer is resumed.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149211(retired)
|
Info: Suspending.
|
Description
| The Slave Deployer is suspending.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149212(retired)
|
Info: Suspended.
|
Description
| The Slave Deployer is suspended.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149213(retired)
|
Info: Shutting down.
|
Description
| The Slave Deployer is shutting down.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149214(retired)
|
Info: Shutdown complete.
|
Description
| The Slave Deployer has shutdown.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149215(retired)
|
Info: Did not receive an initial update after timeout milliseconds.
|
Description
| No additional deployment information was received after timeout milliseconds at startup time.
|
|
Cause
| This is a normal condition and is likely because the managed server has completed all outstanding deployments.
|
|
Action
| No action required.
|
|
|
BEA-149216(retired)
|
Warning: Timed out after timeout milliseconds while waiting for an initial update to complete.
|
Description
| A set of initial deployments were received but did not complete after timeout milliseconds.
|
|
Cause
| This is either because the deployments were large and time consuming, or the administration server disconnected.
|
|
Action
| Verify the status of the deployments targeted for this server and redeploy them if they have failed.
|
|
|
BEA-149217(retired)
|
Error: Unable to obtain the Application Container Factory object.
|
Description
| There is an internal error in the initialization for the server such that the targeted server cannot obtain a reference to the application container factory.
|
|
Cause
| This is serious internal error.
|
|
Action
| Report this error to BEA.
|
|
|
BEA-149218(retired)
|
Error: Attempted to report an exception to DRS and received an error.
|
Description
| This is a serious internal error that should be reported to BEA.
|
|
Cause
| This is an internal error.
|
|
Action
| Report this error to BEA.
|
|
|
BEA-149219(retired)
|
Warning: Cannot deploy an internal management application.
|
Description
| One attempt to retry the deployment of this internal management application will be attempted. If that fails, it is indicative of a serious internal error that should be reported to BEA.
|
|
Cause
| The internal applications used for managing the server were not properly created and could not be loaded.
|
|
Action
| One attempt to retry the deployment of this internal management application will be attempted. If that fails, it is indicative of a serious internal error that should be reported to BEA.
|
|
|
BEA-149220(retired)
|
Emergency: While deploying server resources on server 'server', the following error was encountered: ex
|
Description
| Errors occurred while Deploying Server resources.
|
|
Cause
| This is generally due to configuration errors.
|
|
Action
| Review the exception.
|
|
|
BEA-149221(retired)
|
Error: Could not find the deployment task associated with the DRS version version.
|
Description
| The targeted server was unable to commit the task specified. This is an internal error that should not ever occur. It reflects a serious problem with the configuration of the server.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149222(retired)
|
Error: An attempt to prepare the application defined by object name: objName failed. There is no associated admin MBean for this application.
|
Description
| The admin ApplicationMBean for the given application does not exist.
|
|
Cause
| The admin MBean was deleted, or an RMI failure occurred.
|
|
Action
| Check your deployment request.
|
|
|
BEA-149223(retired)
|
Error: Attempted to report success to DRS and received an error.
|
Description
| This is a serious internal error that should be reported to BEA.
|
|
Cause
| This is an internal error.
|
|
Action
| Report this error to BEA.
|
|
|
BEA-149224(retired)
|
Error: Unable to stage application 'name', due to the following exception: error
|
Description
| The application staging failed.
|
|
Cause
| This error is likely caused due to the unavailability of files in the specified location, or due to a network error.
|
|
Action
| Review the exception and take necessary actions.
|
|
|
BEA-149225(retired)
|
Error: Unable to unpack the application 'name' to the file 'file'.
|
Description
| During the staging of applications that are deployed as directories, the managed server unpacks the contents of the source JAR into a local directory. The server was able to acquire a handle to the remote input stream but was unable to save it to the file system.
|
|
Cause
| An error occurred in the local file system.
|
|
Action
| Review the exception and take any necessary corrective actions.
|
|
|
BEA-149226(retired)
|
Error: Unable to copy the application 'name' to the file 'file'.
|
Description
| During the staging of applications that are deployed as archives, the managed server attempts to make a local copy of the application file. The server was able to acquire a handle to the remote input stream but was unable to save it to the file system.
|
|
Cause
| There is an error in the local file system.
|
|
Action
| Review the exception and take any necessary corrective actions.
|
|
|
BEA-149227(retired)
|
Info: No modules on the application 'name' apply to server 'server'.
|
Description
| The application does not include any modules that are currently targeted to server 'server'.
|
|
Cause
| No module was targeted to the server.
|
|
Action
| Review your deployment request and target the module properly.
|
|
|
BEA-149228(retired)
|
Critical: Change received for version 'newVersion' from DRS, but it is already at version 'oldVersion'.
|
Description
| Version updates need to arrive in order. This error indicates that DRS is invoking prepareUpdate on a deployment that has already been processed.
|
|
Cause
| This is an internal error.
|
|
Action
| Report the error to BEA.
|
|
|
BEA-149229
|
Emergency: Server 'server' in cluster 'cluster' is unable to initialize due to failed deployments.
|
Description
| Clustered servers must successfully deploy all configured applications in order to complete the startup process.
|
|
Cause
| This problem occurred due to failed deployments, which are already logged.
|
|
Action
| Correct the deployment problem and restart the server in the cluster.
|
|
|
BEA-149230(retired)
|
Error: It is not possible to stage individual files for application 'name', which is deployed as an archive.
|
Description
| The staging mechanism that is built into WebLogic Server will not allow the update of individual files into an application that is deployed as an archive.
|
|
Cause
| The staging mechanism that is built into WebLogic Server will not allow the update of individual files into an application that is deployed as an archive.
|
|
Action
| Make sure the application is deployed as an unarchived directory and not as an archived JAR file.
|
|
|
BEA-149231
|
Error: Unable to set the activation state to active for the application 'name'.
|
Description
| There was an internal error and, as a result, the activation state was not properly updated.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-149232(retired)
|
Error: A mismatch exists between the number of components specified, specifiedComponents, and the number of components that exist, actualComponents.
|
Description
| A mismatch exists in the number of components specified and the number of componentMBeans found.
|
|
Cause
| This represents a problem with the internal implementation that was not anticipated.
|
|
Action
| Report the error and any useful information needed to reproduce the problem to BEA.
|
|
|
BEA-149233
|
Error: An unexpected error was encountered during the deployment process.
|
Description
| An unexpected error was encountered during the deployment process.
|
|
Cause
| This represents a problem with the internal implementation that was not anticipated.
|
|
Action
| Report the error and any and useful information needed to reproduce the problem to BEA.
|
|
|
BEA-149234(retired)
|
Error: The server 'server' had an unexpected failure ex while preparing to deploy the applications that were targeted to it.
|
Description
| This is an unexpected error. Report it to BEA support.
|
|
Cause
| Internal error.
|
|
Action
| This is an unexpected error. Report it to BEA support.
|
|
|
BEA-149235(retired)
|
Warning: Deployment task, task, for application, 'application' was canceled.
|
Description
| The deployment of an application was canceled. This is generally due to timeouts of deployments to partitioned cluster members.
|
|
Cause
| Either the administrator explicitly canceled the task or the task timed out.
|
|
Action
| Retry the deployment. Ensure that there is sufficient time out specified in the deployment request.
|
|
|
BEA-149236(retired)
|
Info: Preparing to suspend.
|
Description
| The Deployment Slave is preparing to suspend.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149237(retired)
|
Info: Ready to suspend.
|
Description
| The Deployment Slave is ready to suspend.
|
|
Cause
| This is an information level message.
|
|
Action
| No action required.
|
|
|
BEA-149238(retired)
|
Warning: No application is associated with deployment task ( id = id ): desc.
|
Description
| The deployment task did not specify an existing application.
|
|
Cause
| This is generally due to remove operations where the application has been removed from the system before the task was received by one of its targets.
|
|
Action
| No action required.
|
|
|
BEA-149239
|
Warning: Application deployment failures were detected during startup of the admin server, 'server'; member of cluster 'cluster'.
|
Description
| The admin server is part of a cluster. Normally, deployment failures during startup of cluster members result in an aborted startup. Since this is the admin server, it is allowed to continue. It must be noted that the cluster is now in an inconsistent state, which could result in failed service requests.
|
|
Cause
| One or more applications could not be deployed during the startup of the admin server.
|
|
Action
| It is not recommended to make the admin server part of a cluster. One response to this warning is to remove it from the cluster and restart the admin server. Alternatively, review the admin server log to understand why the deployment failed, fix the problem, and redeploy the application.
|
|
|
BEA-149240(retired)
|
Emergency: Application 'appName' not found. Targeted server was not able to deploy an internal application.
|
Description
| This is a serious internal error that should be reported to BEA.
|
|
Cause
| The internal applications used for managing the server were not properly created and could not be loaded.
|
|
Action
| This is a serious internal error that should be reported to BEA.
|
|
|
BEA-149241(retired)
|
Error: The managed server failed to stage the file 'appName' from the server.
|
Description
| The managed server failed to stage the file from the admin server.
|
|
Cause
| An error occurred on the admin server while trying to retrieve the Alt DD file.
|
|
Action
| Check the status of your admin server.
|
|
|
BEA-149242(retired)
|
Error: The application 'appName' is not currently deployed to 'targetName'. This operation is hence not allowed.
|
Description
| There is no ApplicationContainer found for the application on the server specified.
|
|
Cause
| The application is not targeted to the server.
|
|
Action
| Users needs to take corrective action by specifying the right target.
|
|
|
BEA-149243
|
Warning: The internal application 'appName' could not be deployed. An attempt will be made to retry deploying this application after syncing the application files again.
|
Description
| A problem occurred while deploying the internal application 'appName'.
|
|
Cause
| It is likely that the internal staged directory was corrupt or there was a failure when deploying the staged application.
|
|
Action
| No action is necessary if the retry succeeds. Otherwise, the nature of the failure should provide an indication of the problem and its resolution. If this is not clear, contact BEA Support with the relevant logs and configuration files.
|
|
|
BEA-149244(retired)
|
Error: Encountered an exception while attempting to commit the task task for the application 'application'. Exception is : t
|
Description
| The targeted server was unable to commit the stop task.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149245
|
Error: The deployment plan at 'plan' for application, 'name', does not define a valid deployment plan.
|
Description
| The document in question is not a deployment plan.
|
|
Cause
| The application is configured with an incorrect deployment plan document.
|
|
Action
| Deploy the application using a valid deployment plan.
|
|
|
BEA-149246
|
Error: The security realm 'realm' does not support application versioning. Deployment of application 'app' failed.
|
Description
| The security realm 'realm' configured does not support application versioning, and thus the deployment of the application version failed.
|
|
Cause
| The security realm 'realm' configured does not support application versioning, and thus the deployment of the application version failed.
|
|
Action
| Deploy the application using a security realm that supports application versioning.
|
|
|
BEA-149247
|
Error: Failed to transition the application 'appName' to running mode due to error ex.
|
Description
| The targeted server was unable to transition the application to running mode because the application container encountered an error.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149248
|
Error: Failed to transition the application 'appName' to admin mode due to error ex.
|
Description
| The targeted server was unable to transition the application to admin mode because the application container encountered an error.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149249(retired)
|
Info: Error reported during undeploy for application 'appName' : ex.
|
Description
| This does not affect the undeploy operation.
|
|
|
BEA-149250
|
Error: Unable to unprepare application 'name'.
|
Description
| There was an internal error and, as a result, the application was not properly unprepared.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-149251
|
Warning: Operation operation failed for application 'app'. Error - ex
|
Description
| This is informational, because the container will be moved to the intended state, regardless.
|
|
Cause
| Please see the exception in the message body.
|
|
Action
| Typically, no action is required.
|
|
|
BEA-149252
|
Warning: No deployment 'app' found for Operation operation.
|
Description
| The operation will have no effect.
|
|
Cause
| Please see message body.
|
|
Action
| No action is required.
|
|
|
BEA-149253(retired)
|
Error: Failed to op the application 'application' due to error ex.
|
Description
| The targeted server was unable to op the application because the application container encountered an error.
|
|
Cause
| The cause of this error is likely in the application or the application subsystem for that application type.
|
|
Action
| Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
|
|
|
BEA-149254(retired)
|
Info: Application, 'app', already deployed.
|
Description
| The operation will have no effect.
|
|
Cause
| Please see message body.
|
|
Action
| No action is required.
|
|
|
BEA-149255(retired)
|
Error: Failed to find deployment mbean for Application 'appName'
|
Description
| The targeted server was unable to find deployment mbean for the application 'appName'.
|
|
Cause
| The cause of this error is likely that deployment mbean is not properly created. One possible reason for this would be it may not have proper descriptors.
|
|
Action
| Review the exception and attempt to repair the application level and reinitiate the deployment request.
|
|
|
BEA-149256
|
Error: Failed to find deployment for Application 'appName'
|
Description
| The targeted server was unable to find deployment for the application 'appName'.
|
|
Cause
| The cause of this error is likely that deployment is not properly created. One possible reason for this would be it may not have proper descriptors.
|
|
Action
| Review the exception and attempt to repair the application level and reinitiate the deployment request.
|
|
|
BEA-149257
|
Error: Rejecting attempt to distribute application, 'appName', while the application is running.
|
Description
| Applications must not be stopped prior to redistributing.
|
|
Cause
| The application is not stopped.
|
|
Action
| Stop the application or use redeploy.
|
|
|
BEA-149258
|
Warning: Server failed to remove the staged files 'stageDir' for application 'appName' completely. Check the directory and make sure no other application using this directory. This will result in inappropriate results when this server gets partitioned and trying to deploy this application.
|
Description
| Server failed remove the staged files 'stageDir' for application 'appName' completely. Check the directory and make sure no other application using this directory. This will result in inappropriate results when this server gets partitioned and trying to deploy this application.
|
|
Cause
| Some other application might be using the files under staging directory.
|
|
Action
| Delete the above mentioned staged files manually.
|
|
|
BEA-149259
|
Emergency: Server 'server' in cluster 'cluster' is being brought up in administration state due to failed deployments.
|
Description
| Clustered servers must successfully deploy all configured applications in order to complete the startup process. Startup failure of any configured deployments will cause the server to be brought up in administration state instead.
|
|
Cause
| This problem occurred due to failed deployments, which are already logged.
|
|
Action
| Correct the cause of the deployment error(s), redeploy the failed deployment(s), and resume or restart the server in the cluster.
|
|
|
BEA-149260
|
Error: A failure occurred during application startup.
|
Description
| A failure occurred during application startup.
|
|
Cause
| Please check the error stack trace for details of the failure.
|
|
Action
| Correct the cause of the application failure, if possible, and redeploy the application or restart the server. If it is a BEA internal application, report it to BEA support.
|
|
|
BEA-149261(retired)
|
Warning: Server 'server' is admin server and making loopback connection.
|
Description
| Server 'server' is admin server and making loopback connection.
|
|
Cause
| This probably occurred while staging the descriptor files and server is admin server.
|
|
Action
| Internal error.
|
|
|
BEA-149262(retired)
|
Error: The managed server failed to stage the descriptor file 'descriptorName' for the application 'appName' from the admin server.
|
Description
| The managed server failed to stage the descriptor file 'descriptorName' for the application 'appName' from the admin server.
|
|
Cause
| An error occurred on the admin server while trying to retrieve the descriptor file
|
|
Action
| Check the status of your admin server.
|
|
|
BEA-149263(retired)
|
Warning: Requested uri 'uri' does not exist in the application 'application'. Underlying error is 'originalMsg'.
|
Description
| Requested uri 'uri' does not exist in the application 'application'. Underlying error is 'originalMsg'.
|
|
Cause
| Server received dynamic update deployment or redeploy request for a file that does not exist in the application.
|
|
Action
| Try with a valid uri.
|
|
|
BEA-149264
|
Error: Invalid redeploy attempt on application 'appName'. There was an attempt to redeploy the application when the application is not running.
|
Description
| Invalid redeploy attempt on application 'appName'. There was an attempt to redeploy the application when the application is not running.
|
|
Cause
| Application is stopped.
|
|
Action
| Start the application.
|
|
|
BEA-149265
|
Error: Failure occurred in the execution of deployment request with ID 'requestId' for task 'task'. Error is: 'e'
|
Description
| Unable to finish the task due to an error.
|
|
Cause
| Look at the underlying error.
|
|
Action
| Start the application.
|
|
|
BEA-149266
|
Error: Illegal state for operation deploy: 'state'.
|
Description
| Illegal state for operation deploy: 'state'.
|
|
Cause
| Deploy operation was called on application that was not new.
|
|
Action
| Please verify the specified application name and operation are correct.
|
|
|
BEA-149267
|
Error: Cancel operation on deployment task 'taskid' on server 'server' failed.
|
Description
| Cancel operation on deployment task 'taskid' on server 'server' failed.
|
|
Cause
| See the underlying exception.
|
|
Action
| Take action based on the underlying exception.
|
|
|
BEA-149268
|
Error: Static deployment of non-versioned application 'appName' failed due it its manifest defines version.
|
Description
| Application 'appName' is non-versioned and its manifest defines version. Modifying manifest with a version for non-versioned application is not supported under static deployment.
|
|
Cause
| Manifest modified with version for non-versioned application.
|
|
Action
| Remove application and deploy it again with version.
|
|
