|
BEA-149000
|
Emergency: Unable to create DeployerRuntimeMBean.
|
Description
| Creation of DeployerRuntimeMBean failed.
|
|
Cause
| This may occur if an error at the JMX level exists.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149001
|
Warning: No application named 'app' exists for operation method
|
Description
| Unable to perform the method request for application 'app', since it does not exist.
|
|
Cause
| The application name was likely misspelled.
|
|
Action
| Verify the application is correctly named.
|
|
|
BEA-149002
|
Warning: The source file was not provided for activation of application: 'name'.
|
Description
| No configured application named 'name' exists. Therefore, no source file to create the application configuration was provided in the activate request.
|
|
Cause
| Source files do not exist for the application to be deployed.
|
|
Action
| Make source files available for the application to be deployed in the said path.
|
|
|
BEA-149003
|
Warning: Unable to access application source information in 'file' for application 'name'. The specific error is: err.
|
Description
| The provided source file is not accessible or is not a valid application.
|
|
Cause
| Source files for the application to be deployed are not accessible.
|
|
Action
| Ensure that no other process is using the source file(s).
|
|
|
BEA-149004
|
Warning: Failures were detected while initiating task task for application 'app'.
|
Description
| The named task failed. Specific errors have been logged and are recorded in the associated DeploymentTaskRuntimeMBean.
|
|
Cause
| Task creation can fail for many reasons.
|
|
Action
| Check the error message and take appropriate actions.
|
|
|
BEA-149005(retired)
|
Warning: Unable to change the path for application 'name', to 'src'.
|
Description
| The path was not changed on the ApplicationMBean.
|
|
Cause
| This was an unexpected error.
|
|
Action
| Report the error to BEA support.
|
|
|
BEA-149006(retired)
|
Error: The application 'name' is configured with incompatible target servers.
|
Description
| The application is targeted to incompatible servers.
|
|
Cause
| An attempt was made to target the application to incompatible servers in the domain.
|
|
Action
| Target the application to a compatible server.
|
|
|
BEA-149007
|
Warning: New source location, 'newPath', cannot be deployed to configured application, 'name'. The application source is at 'configPath'. Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.
|
Description
| You cannot specify a new source for a previously configured application with a different source.
|
|
Cause
| This error occurs when you attempt to change the source location for a previously configured application.
|
|
Action
| Deploy your application with the same source location that was configured in the application.
|
|
|
BEA-149008(retired)
|
Error: An exception occurred while attempting to deploy application 'name' to an incompatible server: 'server'.
|
Description
| Applications cannot be targeted to incompatible servers.
|
|
Cause
| The application is already configured with active servers, and an attempt was made to add an incompatible server.
|
|
Action
| Create a separate configuration of this application to deploy to the server.
|
|
|
BEA-149009(retired)
|
Error: An invalid task identifier, task, was specified for a deployment request.
|
Description
| This is an internal error.
|
|
Cause
| This is due to an invalid deployment request.
|
|
Action
| Specify a valid deployment request.
|
|
|
BEA-149010(retired)
|
Error: Target 'target' is not configured. Unable to deploy application 'name'.
|
Description
| Targets in a deployment request must already be configured. The target must be the server, cluster, or virtual host. Virtual hosts may only be targeted by Web components.
|
|
Cause
| The target name 'target' does not exist.
|
|
Action
| Check the spelling of targets in the request and verify they are in the current configuration.
|
|
|
BEA-149011
|
Error: Some of the targets in the deployment request are not configured in this domain. The named targets are: 'targets'.
|
Description
| A deployment request was made to non-configured targets.
|
|
Cause
| This error occurs when a deployment request to non-configured target is made.
|
|
Action
| Ensure that the target list in the request is correct.
|
|
|
BEA-149012(retired)
|
Error: Some of the targets in the request are not compatible with the application 'app'. The new targets are: 'targets'.
|
Description
| The application is already deployed. The request to extend this deployment to incompatible deployments is not supported.
|
|
Cause
| This error occurs when a deployment request to non-configured target is made.
|
|
Action
| Ensure that the target list in the request is correct.
|
|
|
BEA-149013
|
Error: Application 'app' does not define the module, 'module'. validModuleNames are the known valid module(s) for this application.
|
Description
| An attempt to perform a deployment operation on an undefined module was rejected.
|
|
Cause
| Incorrect deployment information was provided in the activate request.
|
|
Action
| Ensure that the module information in the request is accurate. If you are adding modules, make sure that you specify the source file again so that it is reloaded and any new modules are deployed.
|
|
|
BEA-149014
|
Error: Target 'target' is not defined.
|
Description
| An attempt to deploy or deactivate to an unconfigured target was rejected.
|
|
Cause
| Incorrect deployment information was provided in the activate request.
|
|
Action
| Ensure that the target information in the request is accurate.
|
|
|
BEA-149015
|
Warning: Unable to add 'target' to component 'comp'.
|
Description
| A request to deploy a component to a server, cluster, or virtual host could not be completed.
|
|
Cause
| The component is already targeted to the server, cluster, or virtual host.
|
|
Action
| Check your target list.
|
|
|
BEA-149016(retired)
|
Warning: Unable to remove target, 'target', from 'comp'.
|
Description
| A request to deactivate or remove a module on a server, cluster, or virtual host could not be completed.
|
|
Cause
| The module is not targeted to the server, cluster, or virtual host.
|
|
Action
| Check your target list. You cannot deactivate an application from non-targeted servers/clusters.
|
|
|
BEA-149017(retired)
|
Warning: This deployment does not use the two-phase deployment protocol and hence cannot be cancelled.
|
Description
| An attempt was made to cancel a deployment task that does not support that operation.
|
|
Cause
| This error occurred due to an attempt to use the cancel command on a deployment that uses the old style deployment protocol i.e it does not use the new two-phase mechanism.
|
|
Action
| The cancel command only works on deployments using the new two-phase protocol.
|
|
|
BEA-149018(retired)
|
Error: An attempt was made to use an old deployment protocol, method, on application, 'name'. This application is already deployed using the two-phase deployment protocol.
|
Description
| This application is already deployed and cannot be redeployed using a different protocol.
|
|
Cause
| The ApplicationMBean.method method was invoked on this application.
|
|
Action
| Be consistent in your use of deployment protocols.
|
|
|
BEA-149019(retired)
|
Warning: An attempt was made to deploy application 'name' using a deprecated deployment protocol.
|
Description
| This application is configured with servers that do not support two-phase deployment.
|
|
Cause
| This warning results if an application is deployed to servers with versions prior to WLS 7.x.
|
|
Action
| Upgrade your servers configured for this application.
|
|
|
BEA-149020(retired)
|
Info: Application name does not have a source copy on the admin server. Continuing with deployment assuming files already exist on target servers.
|
Description
| The user has configured this application so that it is not staged from the admin server and is taking responsibility for properly configuring the application files manually.
|
|
Cause
| The user is deploying an application but is managing the placement of the application files manually.
|
|
Action
| No action required.
|
|
|
BEA-149021
|
Warning: Rejecting name request for application 'method'. The ID specified, id, is already being used.
|
Description
| Deployment tasks allow the caller to specify an ID to assign to the task. This ID must be unique. The DeployerRuntime.list() method determines which IDs are currently in use.
|
|
Cause
| A method request included an ID provided by a user that is already assigned to another task.
|
|
Action
| Choose a different ID or allow the system to allocate an ID for the request.
|
|
|
BEA-149022(retired)
|
Error: An unexpected error occurred while attempting to set the Deployed attribute on MBean: objName.
|
Description
| An unexpected error occurred while attempting to set the Deployed attribute on ApplicationMBean.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149023(retired)
|
Error: The application 'app' is not configured on server 'server'.
|
Description
| While attempting to deploy the application, the server could not access or create its configuration MBean.
|
|
Cause
| This is an internal error.
|
|
Action
| Report this error to BEA support.
|
|
|
BEA-149024(retired)
|
Error: Unable to save the configuration after deployment processing.
|
Description
| The Deployer was unable to rewrite the configuration file.
|
|
Cause
| An unexpected error occurred while attempting to save the configuration information.
|
|
Action
| No action required. This condition may be temporary.
|
|
|
BEA-149025
|
Error: An invalid attempt was made to target a non-Web application component, 'comp', in application, 'app', to a virtual host, 'target'.
|
Description
| Only Web application modules can be deployed to virtual hosts.
|
|
Cause
| An invalid attempt was made to target a non-Web application to virtual hosts.
|
|
Action
| Correct your target list.
|
|
|
BEA-149026
|
Info: task application app on target.
|
Description
| This is an informational message about the task description.
|
|
Cause
| This is an informational message about the task description.
|
|
Action
| This is an informational message about the task description.
|
|
|
BEA-149027
|
Error: Unable to activate application, 'name', from source, 'src'. Reason: err
|
Description
| An invalid application was found.
|
|
Cause
| The application is improperly defined.
|
|
Action
| Define the application properly.
|
|
|
BEA-149028
|
Error: An invalid path, 'path', was specified for application, 'name'.
|
Description
| The application has a non-existent path.
|
|
Cause
| The configured path for this application does not exist.
|
|
Action
| Provide the application files in the specified location.
|
|
|
BEA-149029(retired)
|
Error: Unable to delete the application from the domain for task: task.
|
Description
| An exception occurred while attempting to delete the application MBean associated with this task. The application was successfully deactivated.
|
|
Cause
| The application MBean has already been deleted.
|
|
Action
| No action required. This is an indication that an attempt was made to delete a previously deleted MBean.
|
|
|
BEA-149030(retired)
|
Warning: Rejecting deployment request for 'name', since no targets apply to the request.
|
Description
| The request is rejected, since no targets apply to the request.
|
|
Cause
| This is an empty deployment request.
|
|
Action
| Specify the configured target for this deployment request.
|
|
|
BEA-149031
|
Error: The stagingMode of 'stagingMode' is invalid. The legal values are "stage" or "nostage".
|
Description
| The request is rejected, since the stagingMode is invalid.
|
|
Cause
| An invalid staging mode has been specified.
|
|
Action
| Specify a valid staging mode for the deployment request.
|
|
|
BEA-149032
|
Error: An attempt to restart a task has been rejected. The task has already been started.
|
Description
| An attempt to restart a task has been rejected.
|
|
Cause
| This error results if start is called on a task that has already been started.
|
|
Action
| Do not call start on a task that has already been started.
|
|
|
BEA-149033
|
Info: state application app on server
|
Description
| An application-level deployment notification has been reported.
|
|
Cause
| An application-level deployment notification has been reported.
|
|
Action
| No action required. This is information-level log message.
|
|
|
BEA-149034
|
Info: An exception occurred for task desc: msg.
|
Description
| An application-level deployment exception has been reported.
|
|
Cause
| An error occurred while reporting the application status.
|
|
Action
| The error may be due to server instability. Check your server health.
|
|
|
BEA-149035
|
Info: Module module reported error: msg.
|
Description
| A module error has been reported.
|
|
Cause
| The deployment request failed.
|
|
Action
| Check the exception log and take appropriate actions.
|
|
|
BEA-149036(retired)
|
Error: A malformed WebLogic Object Name has been reported.
|
Description
| A malformed WebLogic Object Name has been reported. This is an internal failure.
|
|
Cause
| This is an internal error.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149037(retired)
|
Error: An exception occurred while processing the completion of the task desc, ex. The configuration may not have been updated.
|
Description
| All of the targets associated with the task completed. However, the deployment subsystem was unable to complete the configuration persistence.
|
|
Cause
| This is an internal error.
|
|
Action
| No action required. The information that needs to be persisted is in the configuration and will be persisted eventually. This can be forced by changing anything else in the configuration.
|
|
|
BEA-149038
|
Info: Initiating Task for appName : description
|
Description
| This is an information-level message about initiating the deployment task.
|
|
Cause
| This is information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149039(retired)
|
Info: Completing a deployment task with ID id for application appName with status status.
|
Description
| This is an information-level message about the completion of a task.
|
|
Cause
| This is an information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149040
|
Warning: An attempt to change the staging mode for application, 'name' has been rejected.
|
Description
| Once a staging mode has been established for an application, it cannot be changed.
|
|
Cause
| An attempt was made to change the staging mode for the application.
|
|
Action
| You cannot change the staging mode once it is set. Try deploying again without changing the staging mode.
|
|
|
BEA-149041(retired)
|
Warning: The virtual host 'host' that was targeted for the application 'name' contains no targets.
|
Description
| When deploying to a virtual host, this virtual host should have targets already configured.
|
|
Cause
| The specified virtual host does not contain any configured targets.
|
|
Action
| Add one or more servers or clusters to the specified virtual host and retry the deployment.
|
|
|
BEA-149042(retired)
|
Error: Server 'server' was targeted muliple times in the same deployment request.
|
Description
| Server 'server' is part of a cluster or virtual host and was thus included more than once in the same deployment under different targets.
|
|
Cause
| The current implementation of the deployment infrastructure is incapable of tracking this type of request and it is therefore not allowed.
|
|
Action
| Modify the deployment request.
|
|
|
BEA-149043
|
Error: You cannot change the stagingMode for an application that has already been configured. The stagingMode change has been rejected for application 'app', from configuredStagingMode to desiredStagingMode.
|
Description
| You cannot change the stagingMode for an application that has already been configured. The stagingMode change has been rejected for application 'app', from configuredStagingMode to desiredStagingMode.
|
|
Cause
| An attempt was made to change the stagingMode on an application.
|
|
Action
| Try deploying without changing the stagingMode.
|
|
|
BEA-149044(retired)
|
Error: The deployer is unable to access the domain repository to save changes associated with deployment task id: desc.
|
Description
| All of the targets associated with the task completed, but the deployment subsystem was unable to complete persistence of the configuration.
|
|
Cause
| This is an unexpected error.
|
|
Action
| No action required. The deployment information will be persisted in a normal persistence cycle.
|
|
|
BEA-149045
|
Error: An attempt to add cluster target 'cluster' was rejected, since cluster member 'server' is also targeted by module 'module'. Targeting to a cluster member results in different behaviors than targeting the entire cluster.
|
Description
| It is invalid to target a module to a cluster and a member of that cluster.
|
|
Cause
| A cluster member is already in the target list of the module.
|
|
Action
| Remove the cluster member from the target list, or re-target the cluster member rather than the cluster itself.
|
|
|
BEA-149046(retired)
|
Error: An attempt to add cluster target 'cluster' to module 'module' has been rejected, since the cluster target is also targeted through a virtual host 'host'.
|
Description
| The module identifies a virtual host target, which includes the named cluster as one of its members.
|
|
Cause
| The cluster is already targeted to the module by way of a virtual host.
|
|
Action
| Remove the cluster from the target list or remove the cluster from the virtual host.
|
|
|
BEA-149047(retired)
|
Error: An attempt to add cluster target 'cluster' to module 'module' has been rejected. This is because cluster member 'server' is also targeted by way of a virtual host, 'host'.
|
Description
| The module has identified a virtual host target, which includes a member of the named cluster as one of its members.
|
|
Cause
| The cluster is already targeted to the module by way of a virtual host.
|
|
Action
| Remove the cluster from the target list or remove the cluster member from the virtual host.
|
|
|
BEA-149048
|
Error: An attempt to add server target 'server' to module 'module' has been rejected. This is because its parent cluster, 'cluster', is also targeted by the module.
|
Description
| It is invalid to target a cluster and one of its members to the same module.
|
|
Cause
| The module is already targeted to a cluster that contains the server.
|
|
Action
| Remove the cluster from the target list or remove the cluster member from the target list.
|
|
|
BEA-149049(retired)
|
Error: An attempt to add server target 'server' to module 'module' has been rejected. This is because its parent virtual host, 'host', is also targeted by the module.
|
Description
| It is invalid to target a virtual host and one of its members to the same module.
|
|
Cause
| The module is already targeted to a virtual host that contains the server.
|
|
Action
| Remove the host from the target list or remove the server from the virtual host.
|
|
|
BEA-149050(retired)
|
Error: An attempt to add server target 'server' to module 'module' has been rejected. This is because its parent virtual host, 'host', is also targeted by the module by way of a cluster, 'cluster'.
|
Description
| It is invalid to target a virtual host and one of its members to the same module.
|
|
Cause
| The module is already targeted to a virtual host that contains the server.
|
|
Action
| Remove the host from he target list or remove the cluster from the virtual host.
|
|
|
BEA-149051(retired)
|
Error: An attempt to add a virtual host target 'host' to module 'module' has been rejected. This is because it is also targeted by the module by way of a virtual host member, 'server'.
|
Description
| It is invalid to target a virtual host and one of its members to the same module.
|
|
Cause
| The module is already targeted to a server defined for the virtual host.
|
|
Action
| Remove the host from the target list or remove the server from the target list.
|
|
|
BEA-149052(retired)
|
Error: An attempt to add virtual host target 'host' to module 'module' has been rejected. This is because it is also targeted by the module by way of a virtual host member, 'cluster'.
|
Description
| It is invalid to target a virtual host and one of its members to the same module.
|
|
Cause
| The module is already targeted to a cluster defined for the virtual host.
|
|
Action
| Remove the host from the target list or remove the cluster from the target list.
|
|
|
BEA-149053(retired)
|
Error: An attempt to add a virtual host target 'host' to module 'module' has been rejected. This is because it is also targeted by the module by way of a virtual host member, 'server', (a member of cluster, 'cluster' ).
|
Description
| It is invalid to target a virtual host and one of its members to the same module.
|
|
Cause
| The module is already targeted to a cluster member defined for the virtual host.
|
|
Action
| Remove the host from the target list or remove the cluster member from the target list.
|
|
|
BEA-149054
|
Error: An attempt to add a virtual host target 'host' to a non-Web application module 'module' has been rejected.
|
Description
| Only Web applications can have virtual hosts as targets.
|
|
Cause
| An EJB or Connector was attempting to target a virtual host.
|
|
Action
| Remove the host from target list.
|
|
|
BEA-149055
|
Info: Adding server server1 of cluster cluster as a target for module module. This module also includes server server2 that belongs to this cluster as one of its additional targets. Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability. Hence, this is not usually recommended.
|
Description
| Targeting multiple cluster members is not recommended, since it affects load-balancing and cluster scalability.
|
|
Cause
| The module is already targeted to a different cluster member.
|
|
Action
| Target the entire cluster to the module.
|
|
|
BEA-149056(retired)
|
Warning: An unexpected error from 'target' occurred during the processing of deployment task id: desc.
|
Description
| The named target is not part of the deployment, yet a request to update the status for it was received.
|
|
Cause
| This is an unexpected condition.
|
|
Action
| The state of the deployment should be validated by the user. Specifically, the user should ensure the application is targeted as expected.
|
|
|
BEA-149057(retired)
|
Error: No change was specified for application 'appName' for an update request.
|
Description
| An update request must be accompanied by change file(s).
|
|
Cause
| This is an unexpected error.
|
|
Action
| Specify a valid change for the update request.
|
|
|
BEA-149058
|
Error: Distribute can only have stage as its stagingMode. Application 'appName' has stagingMode as its stagingMode.
|
Description
| The distribute option is only valid for the stage stagingMode.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Specify a valid staging name.
|
|
|
BEA-149059
|
Info: Module mod of application app is transitioning from start to target on server server.
|
Description
| This message indicates the start of a deployment phase for the named module. The possible states are unprepared (classes not loaded), prepared (classes loaded), and activated (module is available).
|
|
Cause
| A module is being deployed.
|
|
Action
| No action required.
|
|
|
BEA-149060
|
Info: Module mod of application app successfully transitioned from start to target on server server.
|
Description
| This message indicates the successful completion of a deployment phase for the named module. The possible states are unprepared (classes not loaded), prepared (classes loaded), and activated (module is available).
|
|
Cause
| A module is being deployed.
|
|
Action
| No action required.
|
|
|
BEA-149061
|
Info: Module mod of application app failed to transition from start to target on server server.
|
Description
| Indicates the unsuccessful completion of a deployment phase for the named module. The possible states are unprepared (classes not loaded), prepared (classes loaded), and activated (module is available).
|
|
Cause
| An error was encountered during a module deployment.
|
|
Action
| Details of the specific failure are documented in the associated log entries. Take appropriate actions.
|
|
|
BEA-149062
|
Error: The task containing ID taskID cannot be canceled, since it has already completed execution.
|
Description
| Only a task in the initialized or running state can be canceled.
|
|
Cause
| An attempt has been made to cancel a deployment task that has completed execution.
|
|
Action
| Do not attempt this operation on a completed task.
|
|
|
BEA-149063(retired)
|
Notice: There seems to be some configuration error with application appName. See previous errors for details. The application appName will be removed since its target list is empty.
|
Description
| This message occurs when the remove operation fails and the application is no longer deployed to a target.
|
|
Cause
| This may occur due to a misconfigured application (such as an incorrect path).
|
|
Action
| The application and all its metadata are cleaned up. Reconfigure the application if needed.
|
|
|
BEA-149064(retired)
|
Error: An application cannot be deployed dynamically on an independent managed server.
|
Description
| An application cannot be deployed dynamically on an independent managed server.
|
|
Cause
| An attempt was made to deploy to an application dynamically on an independant managed server.
|
|
Action
| Restart the server as a managed server and attempt the deployment again.
|
|
|
BEA-149065(retired)
|
Error: An incorrect stagingMode, stagingMode, was specified for application 'app'. action can only be called if an application has stage as its stagingMode.
|
Description
| Start can only be called on an application with stage as its stagingMode.
|
|
Cause
| An attempt was made to action. An application that does not have stage as its stagingMode cannot be called.
|
|
Action
| Specify the correct stagingMode.
|
|
|
BEA-149066
|
Error: Unable to deploy application 'appName', because module 'module' does not provide a valid URI.
|
Description
| The configuration of a module in the application is incomplete. It must include a valid URI relative to the application path.
|
|
Cause
| The application is incorrectly configured.
|
|
Action
| Provide a URI for the module, or remove the application from the configuration.
|
|
|
BEA-149067(retired)
|
Error: The module in standalone application 'appName' does not have a valid URI.
|
Description
| The configuration of a module in the application is incomplete. It must include its URI relative to the application path.
|
|
Cause
| The application is incorrectly configured.
|
|
Action
| Either provide a URI for the module or remove the application from the configuration.
|
|
|
BEA-149068
|
Error: This is an unexpected exception.
|
Description
| An unexpected error was encountered.
|
|
Cause
| This is an internal error.
|
|
Action
| No action required.
|
|
|
BEA-149069
|
Info: Deploying app using a deprecated protocol.
|
Description
| An application deployment is being started and will not use the two-phase deployment protocol. The user should note that the application cannot take advantage of features such as application scoping.
|
|
Cause
| The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.
|
|
Action
| No action required.
|
|
|
BEA-149070(retired)
|
Info: Undeploying app using a deprecated protocol.
|
Description
| An application is being undeployed and was not deployed using the two-phase protocol.
|
|
Cause
| The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.
|
|
Action
| No action required.
|
|
|
BEA-149071(retired)
|
Info: Deployment task successfully completed for app.
|
Description
| A deployment task involving the old style deployment protocol successfully completed.
|
|
Cause
| The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.
|
|
Action
| No action required.
|
|
|
BEA-149072(retired)
|
Info: The deployment task failed for app.
|
Description
| A deployment task involving the old style deployment protocol failed.
|
|
Cause
| The application is improperly configured.
|
|
Action
| Check the admin and target server logs for specific error messages.
|
|
|
BEA-149073
|
Warning: The application 'name' has no configured modules.
|
Description
| The application configuration must include configuration information for any modules contained within the application.
|
|
Cause
| The application is improperly configured.
|
|
Action
| The application will be marked as undeployable. After resolving configuration issues with the application, the administrator can retry the deployment.
|
|
|
BEA-149074
|
Info: Successfully completed deployment task: desc
|
Description
| This message indicates the successful completion of an application deployment operation.
|
|
Cause
| A deployment operation was requested.
|
|
Action
| No action required
|
|
|
BEA-149075(retired)
|
Info: Failed deployment task: desc. Last error message in task was: msg.
|
Description
| This message indicates a failed application deployment operation. This message includes the text of the last exception thrown during the operation. The server log should provide additional details on the reason for the failure.
|
|
Cause
| A deployment operation was requested.
|
|
Action
| Examine the server log for related messages. If using the Admin Console, browse to the status detail of the task.
|
|
|
BEA-149076(retired)
|
Info: Failed to update target target for application application. The following exception occurred: ex.
|
Description
| Indicates that a deployment subsystem could not remove the targets for the failed application.
|
|
Cause
| An unexpected exception occurred while updating the target list.
|
|
Action
| Examine the server log for related messages and check your network connection.
|
|
|
BEA-149077(retired)
|
Error: An unexpected error occurred while attempting to preserve the TwoPhase attribute for application, 'name'.
|
Description
| The TwoPhase attribute indicates the deployment protocol to use for this application. This attribute should be preserved in the configuration repository, config.xml. The attempt to do this resulted in an unexpected failure.
|
|
Cause
| This is an unexpected, internal error.
|
|
Action
| No action is required.
|
|
|
BEA-149078
|
Warning: Stack trace for message id
|
Description
| Diagnostic information associated with message id, which was previously logged.
|
|
Cause
| A deployment failure occurred.
|
|
Action
| No action is required.
|
|
|
BEA-149079(retired)
|
Error: An error occurred while removing targets for undeployment task id.
|
Description
| Deployment framework was unable to remove the targets for the associcated undeployment task.
|
|
Cause
| A deployment failure occurred.
|
|
Action
| Check the stacktrace and take the necessary action.
|
|
|
BEA-149080
|
Error: A partial update of an archived application is not allowed. Application 'app' cannot be redeployed.
|
Description
| There was an attempt to partially redeploy an archived application. Partial redeployment of an archived application is not allowed.
|
|
Cause
| There was an attempt to partially redeploy an archived application
|
|
Action
| Try deploying entire application
|
|
|
BEA-149081
|
Error: You cannot operation application, 'app', with version 'newVersion'. The application was previously deployed without version.
|
Description
| You cannot operation application, 'app', with version 'newVersion'. The application was previously deployed without version.
|
|
Cause
| An attempt was made to operation a versioned application when it was previously deployed without version.
|
|
Action
| Try operation without version.
|
|
|
BEA-149082
|
Error: You cannot operation application 'app' without version. The application was previously deployed with version 'oldVersion'.
|
Description
| You cannot operation application 'app' without version. The application was previously deployed with version 'oldVersion'.
|
|
Cause
| An attempt was made to operation an application without version when it was previously deployed with version.
|
|
Action
| Try operation with version.
|
|
|
BEA-149085
|
Warning: No application version was specified for application 'app'. The method operation will be performed against the currently active version 'version'.
|
Description
| No application version was specified for application 'app'. The method operation will be performed against the currently active version 'version'.
|
|
Cause
| No application version was specified for the operation.
|
|
Action
| Verify that currently active version is the desired version for the operation. If not, perform the operation again with the -app_version operation to specify a particular version.
|
|
|
BEA-149086
|
Info: The application appName is being retired gracefully.
|
Description
| This is an information-level message about the retirement of an application.
|
|
Cause
| This is an information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149087
|
Info: The application appName will be retired after timeout seconds.
|
Description
| This is an information-level message about the retirement of an application.
|
|
Cause
| This is an information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149088
|
Info: The retirement for application appName, which was scheduled to happen after remainingSecs seconds, is cancelled.
|
Description
| This is an information-level message about the cancellation of retirement of the application. Probably the retirement is cancelled due to a request to redeploy or undeploy the application version.
|
|
Cause
| This is an information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149089
|
Error: An attempt was made to activate the application 'appName' when retirement is in progress.
|
Description
| An attempt was made to activate the application 'appName' when retirement is in progress.
|
|
Cause
| An attempt was made to activate the application 'appName' when retirement is in progress.
|
|
Action
| Try to activate the application 'appName' again after the retirement is done. If it is a graceful retirement, an undeploy can be performed to end the graceful retirement immediately.
|
|
|
BEA-149090(retired)
|
Error: An attempt to create security version for application 'app' failed.
|
Description
| An attempt to create security version for application 'app' failed.
|
|
Cause
| An attempt to create security version for application 'app' failed.
|
|
Action
| Check the server log for additional security error messages, correct security errors, and try again.
|
|
|
BEA-149091
|
Error: An attempt was made to deploy application 'appName' with specified archive version 'expectedVersion'. However, the application archive as specified in the source has version 'manifestVersion'.
|
Description
| You cannot specify a version that is different from the manifest version of the application archive in the source location.
|
|
Cause
| This error occurs when you attempt to specify a version that is different from the manifest version of the application archive in the source location.
|
|
Action
| Perform deployment again without specifying the version, or specifying version 'manifestVersion' instead of 'expectedVersion'.
|
|
|
BEA-149092
|
Error: The source is not specified for the deployment operation of application 'appName', and the expected version is 'mbeanVersion'. However, the application archive at the source location for a previous deployment of version 'mbeanVersion' now has version 'srcVersion'.
|
Description
| The manifest version of the application archive at the source location previously configured for the version is different from the version.
|
|
Cause
| The source is not specified for the deployment operation of application 'appName', and the expected version is either explicitly specified or the currently active version. However, the application archive at the previously configured source location of the expected version has a different manifest version.
|
|
Action
| Perform deployment again specifying either the source location or version 'srcVersion'.
|
|
|
BEA-149093
|
Error: No version specified for versioned application named 'appName' for operation operation, and no active version is available.
|
Description
| Unable to perform the operation request for versioned application 'appName', since a version is not specified and there is no currently active version.
|
|
Cause
| Version is not specified for the operation when no currently active version is available.
|
|
Action
| Specify the version of the application for the operation.
|
|
|
BEA-149094
|
Error: New version 'newVersion' of application 'name' cannot be deployed to the source location, 'path'. The source location is the same as the nostage source location of a previously deployed application version 'oldVersion'.
|
Description
| You cannot specify a new source for a new application version that is the same as the nostage source of a previous application version.
|
|
Cause
| This error occurs when you attempt to deploy a new application version with the same source location as the nostage source location of a previous application version.
|
|
Action
| Deploy your new application version with a different source location. Also make sure that the old application source is still available at the old nostage source location.
|
|
|
BEA-149095
|
Info: The application appName is being retired now.
|
Description
| This is an information-level message about the retirement of an application.
|
|
Cause
| This is an information-level message.
|
|
Action
| No action required.
|
|
|
BEA-149096
|
Error: Operation deprecatedOp is deprecated and cannot be applied to versioned application 'appName'. Please use operation suggestedOp instead.
|
Description
| An attempt was made to perform the deprecated operation deprecatedOp on a versioned application. Please use operation suggestedOp instead.
|
|
Cause
| An attempt was made to perform the deprecated operation deprecatedOp on a versioned application. Please use operation suggestedOp instead.
|
|
Action
| Use operation suggestedOp instead.
|
|
|
BEA-149097
|
Error: The retirement for application 'appName' failed.
|
Description
| The retirement for application 'appName' failed.
|
|
Cause
| This may happen due to a problem in accessing the persistent store or an internal error.
|
|
Action
| Contact BEA support.
|
|
|
BEA-149098
|
Error: An attempt was made to gracefully undeploy the application 'appName' when retirement is in progress.
|
Description
| An attempt was made to gracefully undeploy the application 'appName' when retirement is in progress.
|
|
Cause
| An attempt was made to gracefully undeploy the application 'appName' when retirement is in progress.
|
|
Action
| To stop the graceful retirement, use force undeploy.
|
|
|
BEA-149099
|
Warning: Unexpected errors occurred while sending deployment event eventType on behalf of application 'appName'.
|
Description
| Unexpected errors occurred while sending deployment event eventType on behalf of application 'appName'.
|
|
Cause
| Deployment event listener(s) registered to receive deployment event throw(s) unexpected exception(s) when processing deployment event eventType on behalf of application 'appName'.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149100
|
Warning: Unexpected errors occurred while sending a vetoable deployment event on behalf of application 'appName'.
|
Description
| Unexpected errors occurred while sending a vetoable deployment event on behalf of application 'appName'.
|
|
Cause
| Deployment event listener(s) registered to receive vetoable deployment event throw(s) unexpected exception(s) when processing deployment event t on behalf of application 'appName'.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149101
|
Warning: Application 'app' is not deployed on target 'target'. Hence it cannot be Undeployed / Removed. The requested operation task is valid only on the deployed targets of the application.
|
Description
| Application 'app' is not deployed on target 'target'. Hence it cannot be Undeployed / Removed. The requested operation task is valid only on the deployed targets of the application.
|
|
Cause
| Incorrect target information provided in the task operation request.
|
|
Action
| Ensure that the target information in the request is accurate.
|
|
|
BEA-149102
|
Error: Production Redeployment is not supported for application 'appName', which is of module type moduleType. Production redeployment is supported for the following module types only: supportedModuleTypes. If you are not attempting to perform production redeployment, try deploying without version.
|
Description
| Production Redeployment is not supported for application 'appName', which is of module type moduleType. Production redeployment is supported for the following module types only: supportedModuleTypes. If you are not attempting to perform production redeployment, try deploying without version.
|
|
Cause
| Attempting to perform production redeployment for an unsupported module type.
|
|
Action
| Ensure that the module type is supported before performing production redeployment. Or, try deploying again without version.
|
|
|
BEA-149103
|
Error: An exception occurred while executing task desc for application 'app': ex.
|
Description
| An exception occurred while executing task desc for application 'app': ex.
|
|
Cause
| An exception occurred while executing the deployment task for the application.
|
|
Action
| If it is an application error, correct it if possible. If it is a system error, contact BEA Support.
|
|
|
BEA-149104
|
Error: Update request for 'app' does not specify any descriptors to be updated
|
Description
| The deployment operation requires a list of descriptor URIs. These URIs are based on the deployment plan content.
|
|
Cause
| The deployment plan does not include any module overrides
|
|
Action
| Ensure the deployment plan is properly constructed.
|
|
|
BEA-149105
|
Error: An attempt was made to deploy a library located at 'source' with name 'libName' that is different from the one specified in the manifest of the library: 'manifestLibName'.
|
Description
| You cannot specify a name that is different from the one in the manifest of the library in the source location.
|
|
Cause
| This error occurs when you attempt to specify a name that is different from the one in the manifest of the library in the source location.
|
|
Action
| Perform deployment again without specifying the name of the library.
|
|
|
BEA-149106
|
Error: An attempt was made to deploy a library located at 'source' without specifying a name, and the library does not have "Extension-Name" specified in its manifest.
|
Description
| You cannot deploy a library without specifying a name, if the library does not have a name specified in its manifest, using the "Extension-Name" attribute.
|
|
Cause
| This error occurs when you attempt to deploy a library without specifying a name, and the library module does not have "Extension-Name" specified in its manifest.
|
|
Action
| Perform deployment again specifying the name of the library either during deployment or in the manifest of the library, using the "Extension-Name" attribute.
|
|
|
BEA-149107
|
Error: An attempt was made to deploy library 'appName' with specified specification version 'specifiedSpecVersion' and implementation version 'specifiedImplVersion'. However, the library manifest has specification version 'manifestSpecVersion' and implementation version 'manifestImplVersion'.
|
Description
| You cannot specify a version that is different from the manifest version of the library.
|
|
Cause
| This error occurs when you attempt to specify a version that is different from the manifest version of the library.
|
|
Action
| Perform deployment again without specifying the version, or specifying the same version as specified in the manifest.
|
|
|
BEA-149108
|
Warning: Failures were detected while initiating task task.
|
Description
| The named task failed. Specific errors have been logged and are recorded in the associated DeploymentTaskRuntimeMBean.
|
|
Cause
| Task creation can fail for many reasons.
|
|
Action
| Check the error message and take appropriate actions.
|
|
|
BEA-149109(retired)
|
Warning: An attempt to cancel the pending graceful pendingTaskType task for application 'appName' failed.
|
Description
| An attempt to cancel the pending graceful pendingTaskType task for application 'appName' failed.
|
|
Cause
| The cancellation of the pending graceful pendingTaskType task for application 'appName' failed.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149110
|
Error: An exception occurred while processing the completion of the task desc, ex. The active application version state may not have been updated.
|
Description
| All of the targets associated with the task completed. However, the deployment subsystem was unable to complete the persistence of the active application version state.
|
|
Cause
| This is an internal error.
|
|
Action
| Report this problem to BEA support.
|
|
|
BEA-149111
|
Error: Application 'appName' is non-versioned, and an attempt was made to redeploy application 'appName' with source. Redeploying with source is only allowed for redeploying a new version of a versioned application. Try redeploying again without specifying source.
|
Description
| Application 'appName' is non-versioned, and an attempt was made to redeploy application 'appName' with source. Redeploying with source is only allowed for redeploying a new version of a versioned application. Try redeploying again without specifying source.
|
|
Cause
| An attempt was made to redeploy with source specified for a non-versioned application 'appName'. Redeploy again without specifying source.
|
|
Action
| Try redeploying again without specifying source.
|
|
|
BEA-149112
|
Error: Application 'appName' is already deployed, and an attempt was made to redeploy application 'appName' again with source. Redeploying with source is only allowed for redeploying a new version of the application. Try redeploying again without specifying source or with a new version.
|
Description
| Application 'appName' is already deployed, and an attempt was made to redeploy application 'appName' again with source. Redeploying with source is only allowed for redeploying a new version of the application. Try redeploying again without specifying source or with a new version.
|
|
Cause
| An attempt was made to redeploy with source specified for application 'appName', and application 'appName' is already deployed. Redeploy again without specifying source or with a new version.
|
|
Action
| Try redeploying again without specifying source or with a new version.
|
|
|
BEA-149113
|
Error: Cannot deploy or redeploy application 'appId' because the maximum number of application versions (maxAppVersions) for application 'appName' is exceeded. Currently deployed versions are: 'curVersions'.
|
Description
| Cannot deploy or redeploy application 'appId' because the maximum number of application versions (maxAppVersions) for application 'appName' is exceeded.
|
|
Cause
| An attempt was made to deploy or redeploy application 'appId' when the maximum number of application versions ('maxAppVersions') for application 'appName' is exceeded.
|
|
Action
| Try undeploying existing application version(s) before deploying or redeploying new version(s).
|
|
|
BEA-149114
|
Error: Cannot deploy or redeploy application 'appName' with version identifier 'versionId' because the maximum length of the version identifier (maxVersionIdLength) is exceeded.
|
Description
| Cannot deploy or redeploy application 'appName' with version identifier 'versionId' because the maximum length of the version identifier (maxVersionIdLength) is exceeded.
|
|
Cause
| An attempt was made to deploy or redeploy application 'appName' with version identifier 'versionId' that exceeds the maximum length (maxVersionIdLength).
|
|
Action
| Try reducing the version identifier length when deploying or redeploying the application version.
|
|
|
BEA-149115
|
Error: Cannot deploy or redeploy application 'appName' with invalid version identifier 'versionId'. Version identifiers may only contain alphanumerics, period, underscore, and hyphen, and be less than 215 characters in length.
|
Description
| Cannot deploy or redeploy application 'appName' with invalid version identifier 'versionId'. Version identifiers may only contain alphanumerics, period, underscore, and hyphen, and be less than 215 characters in length.
|
|
Cause
| An attempt was made to deploy or redeploy application 'appName' with invalid version identifier 'versionId'.
|
|
Action
| Try changing the version identifier to a valid one when deploying or redeploying the application version. Version identifiers can only be consisted of alphanumeric, period, underscore, or hyphen character, and must not be . or ...
|
|
|
BEA-149116
|
Error: Cannot obtain the deployment configuration.
|
Description
| Cannot obtain the deployment configuration.
|
|
Cause
| This is an internal error.
|
|
Action
| Contact BEA support.
|
|
|
BEA-149117
|
Info: task library app on target.
|
Description
| This is an informational message about the task description.
|
|
Cause
| This is an informational message about the task description.
|
|
Action
| This is an informational message about the task description.
|
|
|
BEA-149118
|
Error: 'app' is not targeted to 'target'.
|
Description
| Targets are verified prior to attempting undeploy an application.
|
|
Cause
| An attempt was made to undeploy the application from a target where it is not deployed
|
|
Action
| Correct target list for the operation
|
|
|
BEA-149119
|
Error: You cannot specify different targets when deploying a new version 'newVersion' of application 'app'. The target(s) specified, 'newTargets', is/are different from those of the previous version, 'oldTargets'.
|
Description
| You cannot specify different targets when deploying a new version 'newVersion' of application 'app'. The target(s) specified, 'newTargets', is/are different from those of the previous version, 'oldTargets'.
|
|
Cause
| An attempt was made to deploy a new application version with target(s) that is/are different from those of the previous version.
|
|
Action
| Try deploying again without specifying targets, or specify exactly the same targets as previous version.
|
|
|
BEA-149120
|
Error: You cannot specify plan version, 'planVersion', when deploying non-versioned application 'app'.
|
Description
| You cannot specify plan version, 'planVersion', when deploying non-versioned application 'app'.
|
|
Cause
| An attempt was made to deploy a non-versioned application with a plan version.
|
|
Action
| Try deploying again with an application version, or without the plan version.
|
|
|
BEA-149121
|
Error: Rejecting action request for application appName because the deployment service is not started.
|
Description
| Deployment actions cannot be performed when the deployment service is not started.
|
|
Cause
| A deployment operation is attempted when the server is starting up or shutting down.
|
|
Action
| Perform the deployment operation again after the server is up or before the server is shut down.
|
|
|
BEA-149122
|
Error: Deployment Operations on internal application "name",not permitted;.
|
Description
| You cannot perform any Deployment Operations on internal applications
|
|
Cause
| Deployment Operations not permitted on internal applications
|
|
Action
| Do not attempt any deployment operations on internal applications.
|
|
|
BEA-149123
|
Warning: The application "appName" currently has security model "oldModel", and an attempt was made to redeploy the application again with a different security model "newModel". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.
|
Description
| The application "appName" currently has security model "oldModel", and an attempt was made to redeploy the application again with a different security model "newModel". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.
|
|
Cause
| An attempt was made to redeploy the same application (version) with a different security model.
|
|
Action
| Undeploy the application (version) and deploy it again with the new security model.
|
|
|
BEA-149124
|
Warning: Failures were detected while initiating task task for application 'app'. Error is: 'error'
|
Description
| Failures were detected while initiating task task for application 'app'. Error is: 'error'
|
|
Cause
| Task creation can fail for many reasons.
|
|
Action
| Check the error message and take appropriate actions.
|
|
|
BEA-149125
|
Info: No application version was specified for the op operation of application 'appName'. The op operation will be performed against the retired application version 'version'.
|
Description
| No application version was specified for the op operation of application 'appName'. The op operation will be performed against the retired application version 'version'.
|
|
Cause
| This is an informational message only.
|
|
Action
| No action required.
|
|
|
BEA-149126
|
Warning: No application version was specified for the op operation of application 'appName'. The application version 'version' will not be removed as its retirement is still in progress. It is recommended that the application version 'version' be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, users should exercise caution as this may interrupt in-flight work.
|
Description
| No application version was specified for the op operation of application 'appName'. The application version 'version' will not be removed as its retirement is still in progress. It is recommended that the application version 'version' be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, users should exercise caution as this may interrupt in-flight work.
|
|
Cause
| No application version was specified for the op operation of application 'appName'.
|
|
Action
| No action required.
|
|
|
BEA-149127
|
Warning: Failures were detected while initiating 'task' task. Error is: 'error'
|
Description
| Failures were detected while initiating 'task' task. Error is: 'error'
|
|
Cause
| Task creation can fail for many reasons.
|
|
Action
| Check the error message and take appropriate actions.
|
|
|
BEA-149128
|
Info: The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the retired application version 'version'.
|
Description
| The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the retired application version 'version'.
|
|
Cause
| This is an informational message only.
|
|
Action
| No action required.
|
|
|
BEA-149129
|
Info: The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the retiring application version 'version'. Note that retirement is still in progress for version 'version' and any in-flight work will be interrupted.
|
Description
| The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the retiring application version 'version'. Note that retirement is still in progress for version 'version' and any in-flight work will be interrupted.
|
|
Cause
| This is an informational message only.
|
|
Action
| No action required.
|
|
|
BEA-149130
|
Info: The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the currently active version 'version'.
|
Description
| The 'removeAllOpt' option was specified for the removeOp operation of application 'appName'. The removeOp operation will be performed against the currently active version 'version'.
|
|
Cause
| This is an informational message only.
|
|
Action
| No action required.
|
|
|
BEA-149131
|
Error: Cannot perform operation method because application 'app' is in state state
|
Description
| Cannot perform operation method because application 'app' is in state state
|
|
Cause
| The application is no longer active.
|
|
Action
| Make sure the application is active. Deploy again if needed.
|
|
|
BEA-149132
|
Error: Split-dir application appName can only be deployed to the Admin Server
|
Description
| Split dir applications are a development mode feature, such applications are intended to be deployed only on the Admin Server
|
|
Cause
| Attempt to perform deployment operation on Split-dir application on a server other than the Admin Server
|
|
Action
| For split-dir application appName perform deployment operations on the admin-server alone
|
|
|
BEA-149133
|
Error: Auto-deployed application appName can only be deployed to the Admin Server
|
Description
| Auto deployed applications are a development mode feature, such applications intended to be deployed only on the Admin Server
|
|
Cause
| Attempt to perform deployment operation on auto-deployed application on a server other than the Admin Server
|
|
Action
| For Auto-deployed application appName perform deployment operations on the admin-server alone
|
|
|
BEA-149134
|
Error: A redeploy is performed without specifying -source for archived versioned application 'app'. Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.
|
Description
| A redeploy is performed without specifying -source for archived versioned application 'app'. Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.
|
|
Cause
| An attempt was made to partially redeploy an archived application.
|
|
Action
| Specify -source for production redeployment, or redeploy the entire application.
|
|
|
BEA-149135
|
Error: Operation taskType cannot be performed since Application 'app' is not deployed on the target 'target'.
|
Description
| Operation taskType cannot be performed since Application 'app' is not deployed on the target 'target'.
|
|
Cause
| Operation taskType attempt was made on an application which is not deployed on provided target.
|
|
Action
| Try with a valid target.
|
|
|
BEA-149136(retired)
|
Error: Application 'app' is targeted to cluster 'cluster' and provided target for undeploy operation is 'target'. Undeploying application from one or some servers of cluster is not supported.
|
Description
| Application 'app' is targeted to cluster 'cluster' and provided target for undeploy operation is 'target'. Undeploying application from one or some servers of cluster is not supported.
|
|
Cause
| Undeploy operation attempt was made on one or some servers in the cluster when application targeted to cluster.
|
|
Action
| Try with cluster target.
|
|
|
BEA-149137
|
Error: file is an invalid path for partial redeployment. The URI of the file/directory to be redeployed should be relative to root, the root of the enterprise application or standalone module being redeployed.
|
Description
| The URI of the file/directory to be redeployed should be relative to the root of the enterprise application or standalone module being redeployed.
|
|
Cause
| The file could not be located in the application
|
|
Action
| Use a valid file specification for the file
|
|
|
BEA-149138
|
Error: You have specified a subset of the originally configured targets for the application 'app'. This can potentially lead to out of sync applications between the different server targets. The target(s) specified, 'newTargets', is/are different from those of the previous version, 'oldTargets'.
|
Description
| You have specified a subset of the originally configured targets for the application 'app'. This can potentially lead to out of sync applications between the different server targets. The target(s) specified, 'newTargets', is/are different from those of the previous version, 'oldTargets'.
|
|
Cause
| A deployment operation was performed on an existing application with a subset of the originally configured targets.
|
|
Action
| If the application content has changed since the last operation, make sure that you update all configured targets. To do so repeat the operation without specifying targets in order to automatically use the configured targets.
|
|
|
BEA-149139
|
Warning: Application 'app' is targeted to cluster 'cluster' and provided target for operation operation is 'target'. The operation operation on a subset of the targeted clustered servers is not supported.
|
Description
| Application 'app' is targeted to cluster 'cluster' and provided target for operation operation is 'target'. The operation operation on a subset of the targeted clustered servers is not supported.
|
|
Cause
| The operation operation was attempted on one or some servers in the cluster when application targeted to cluster.
|
|
Action
| Try with cluster target. Or undeploy from cluster and deploy to desired individual servers.
|
|
|
BEA-149140
|
Info: The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.
|
Description
| The user is the current owner of the domain configuration edit lock and must activate it before any deployment tasks can proceed.
|
|
Cause
| User is the current owner of the domain configuration edit lock.
|
|
Action
| Activate (or cancel) the edit session. The user can exit the deployer tool without affecting the task.
|
|
|
BEA-149141
|
Error: The AppDeploymentMBean already exists for application 'appName'
|
Description
| The AppDeploymentMBean already exists for application 'appName'
|
|
Cause
| The AppDeploymentMBean already exists for application 'appName'
|
|
Action
| Ensure different applications do not have the same name.
|
|
|
BEA-149142
|
Info: Cluster target 'theTarget' is configured with no servers and hence configuration is updated.
|
Description
| Cluster target 'theTarget' is configured with no servers and hence configuration is updated.
|
|
Cause
| A deployment to a cluster target was attempted while the cluster contains no servers.
|
|
Action
| None.
|
|
|
BEA-149143
|
Error: Submodule targets in an application must be specified with the correct module name.
|
Description
| Submodule targets in an application must be specified with the correct module name.
|
|
Cause
| A submodule target was specified incorrectly.
|
|
Action
| Make sure that the submodule target was specified with the correct syntax with the correct module name.
|
|
|
BEA-149144(retired)
|
Error: Submodule targets in a standalone module must be specifed with the correct application name, but without the module name.
|
Description
| Submodule targets in a standalone module must be specifed with the correct application name, but without the module name.
|
|
Cause
| A submodule target was specified incorrectly.
|
|
Action
| Make sure that the submodule target was specified with the correct syntax for a standalone module deployment.
|
|
|
BEA-149145
|
Info: Unable to contact 'server'. Deployment is deferred until 'server' becomes available.
|
Description
| Unable to contact 'server'. Deployment is deferred until 'server' becomes available.
|
|
Cause
| Unable to contact 'server'. Deployment is deferred until 'server' becomes available.
|
|
Action
| No action necessary.
|
|
|
BEA-149146
|
Info: Attempt to reach admin server with alternate URL: 'nextAdminURL' failed.
|
Description
| Attempt to reach admin server with alternate URL: 'nextAdminURL' failed.
|
|
Cause
| Attempt to reach admin server with alternate URL: 'nextAdminURL' failed.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149147
|
Warning: Could not reach the admin server via any of its URLS: 'urls'.
|
Description
| Could not reach the admin server via any of its URLS: 'urls'.
|
|
Cause
| Could not reach the admin server via any of its URLS: 'urls'.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149148
|
Warning: Exception receiving message on loopback.
|
Description
| Exception receiving message on loopback.
|
|
Cause
| Exception receiving message on loopback.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149149
|
Warning: Malformed URL: 'url'.
|
Description
| Malformed URL: 'url'.
|
|
Cause
| Malformed URL: 'url'.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149150
|
Warning: An IOException occurred while reading input.
|
Description
| An IOException occurred while reading input.
|
|
Cause
| An IOException occurred while reading input.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149151
|
Error: Could not find a registered DeploymentReceiver to handle requests for 'id'.
|
Description
| Could not find a registered DeploymentReceiver to handle requests for 'id'.
|
|
Cause
| Could not find a registered DeploymentReceiver to handle requests for 'id'.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149152
|
Error: No deployment request to set up context for.
|
Description
| No deployment request to set up context for.
|
|
Cause
| No deployment request to set up context for.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149153
|
Warning: A "prepare" message was received for id 'id' that has already been completed or cancelled.
|
Description
| A "prepare" message was received for id 'id' that has already been completed or cancelled.
|
|
Cause
| A "prepare" message was received for id 'id' that has already been completed or cancelled.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149154
|
Warning: A "get deployments response" message was received for id 'id' that has no request - it may have already completed or have been canceled.
|
Description
| A "get deployments response" message was received for id 'id' that has no request - it may have already completed or have been canceled.
|
|
Cause
| A "get deployments response" message was received for id 'id' that has no request - it may have already completed or have been canceled.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149155
|
Warning: Received "get deployments response" message 'id' while already handling one - ignoring the second request.
|
Description
| Received "get deployments response" message 'id' while already handling one - ignoring the second request.
|
|
Cause
| Received "get deployments response" message 'id' while already handling one - ignoring the second request.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149156
|
Error: Illegal state for operation start: 'state'.
|
Description
| Illegal state for operation start: 'state'.
|
|
Cause
| Start operation was called on an application that either had an update pending or was used with the admin mode flag.
|
|
Action
| To move the application from active to adminmode, please use the stop operation.
|
|
|
BEA-149157
|
Info: There is nothing to do for task 'id'.
|
Description
| There is nothing to do for task 'id'.
|
|
Cause
| There is nothing to do for task 'id'.
|
|
Action
| None.
|
|
|
BEA-149158
|
Info: No application files exist at 'filename'.
|
Description
| No application files exist at 'filename'.
|
|
Cause
| No application files exist at 'filename'.
|
|
Action
| None.
|
|
|
BEA-149159
|
Error: There was an attempt to create a staging directory that is null.
|
Description
| There was an attempt to create a staging directory that is null.
|
|
Cause
| There was an attempt to create a staging directory that is null.
|
|
Action
| Make sure the staging directory is properly configured. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149160
|
Error: There was an attempt to create a staging directory for a null application name.
|
Description
| There was an attempt to create a staging directory for a null application name.
|
|
Cause
| There was an attempt to create a staging directory for a null application name.
|
|
Action
| Make sure the application name is properly configured. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149161
|
Error: This operation requires that a target be specified.
|
Description
| This operation requires that a target be specified.
|
|
Cause
| This operation requires that a target be specified.
|
|
Action
| Ensure that the deployment request is complete and contains the required targeting information.
|
|
|
BEA-149162
|
Error: This operation requires that a deployment plan be specified.
|
Description
| This operation requires that a deployment plan be specified.
|
|
Cause
| This operation requires that a deployment plan be specified.
|
|
Action
| Ensure that the deployment request is complete and contains the required deployment plan information.
|
|
|
BEA-149163
|
Warning: The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.
|
Description
| The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed.
|
|
Cause
| The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed.
|
|
Action
| Ensure the domain edit lock is available, and try again. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149164
|
Warning: The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
|
Description
| The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
|
|
Cause
| The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.
|
|
Action
| Ensure the domain edit lock is available, and try again. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149165
|
Warning: Invalid target specified.
|
Description
| Invalid target specified.
|
|
Cause
| Invalid target specified.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149166
|
Warning: Deployments cannot be triggered via configuration updates and via the Deployment APIs simultaneously.
|
Description
| Deployments cannot be triggered via configuration updates and via the Deployment APIs simultaneously.
|
|
Cause
| Deployments cannot be triggered via configuration updates and via the Deployment APIs simultaneously.
|
|
Action
| Ensure the domain edit lock is available, and try again. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149167
|
Info: Nothing to do to commit request for 'name' on 'server'.
|
Description
| Nothing to do to commit request for 'name' on 'server'.
|
|
Cause
| Nothing to do to commit request for 'name' on 'server'.
|
|
Action
| None
|
|
|
BEA-149168
|
Warning: Request 'id' has already been completed or cancelled.
|
Description
| Request 'id' has already been completed or cancelled.
|
|
Cause
| Request 'id' has already been completed or cancelled.
|
|
Action
| Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149169
|
Info: Requires server restart for completion.
|
Description
| Requires server restart for completion.
|
|
Cause
| Requires server restart for completion.
|
|
Action
| Restart the required servers.
|
|
|
BEA-149170
|
Error: Invalid targeting specified for this operation. Module and submodule targets cannot both be specified for this type of request.
|
Description
| Submodule updates are managed differently than module redeployment and cannot be processed together.
|
|
Cause
| The operation specifies both module and submodule targeting, which is invalid for this operation.
|
|
Action
| Perform the operation separately for module and submodule targets
|
|
|
BEA-149171
|
Info: Deferred deployment task: desc
|
Description
| This message indicates the that the task is completed but it is deferred on some of the targets that are unreachable.
|
|
Cause
| A deployment operation was requested with targets that are unreachable
|
|
Action
| No action required
|
|
|
BEA-149172
|
Info: Deployment request requestId affecting system resource bean involves a non dynamic property property in sourceBean and hence will require a restart of the resource or the appropriate server targets for the changes to be active.
|
Description
| Deployment request requestId affecting system resource bean involves a non dynamic property property in sourceBean and hence will require a restart of the resource or the appropriate server targets for the changes to be active.
|
|
Cause
| This is an informational message indicating that a deployment involves a non-dynamic property
|
|
Action
| This is an informational message indicating that a deployment involves a non-dynamic property
|
|
|
BEA-149173(retired)
|
Warning: Library at 'path' has a name that already exists: 'name' with the same version 'version' at 'configuredPath'. This library will not be deployed.
|
Description
| Library at 'path' has a name that already exists: 'name' with the same version 'version' at 'configuredPath'. This library will not be deployed.
|
|
Cause
| The librarys name conflicts with a previous deployment.
|
|
Action
| Rename the library or application that interferres with the required deployment.
|
|
|
BEA-149174(retired)
|
Error: Unable to configure platform domain libraries due to: 't}'.
|
Description
| Unable to configure platform domain libraries due to: 't}'.
|
|
Cause
| Unable to configure platform domain libraries due to: 't}'.
|
|
Action
| See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-149175(retired)
|
Warning: The platform library directories have been overridden with an invalid value 'paths'. As a result this server cannot configure the local platform libraries correctly and applications relying on such libraries will not function correctly.
|
Description
| The platform library directories have been overridden with an invalid value 'paths'. As a result this server cannot configure the local platform libraries correctly and applications relying on such libraries will not function correctly.
|
|
Cause
| The platform library directories have been overridden with an invalid value 'paths'. As a result this server cannot configure the local platform libraries correctly and applications relying on such libraries will not function correctly.
|
|
Action
| The platform library directories have been overridden with an invalid value 'paths'. As a result this server cannot configure the local platform libraries correctly and applications relying on such libraries will not function correctly.
|
|
|
BEA-149176(retired)
|
Warning: The platform library 'libSource' was not found in the platform directories: 'paths'.
|
Description
| The platform library 'libSource' was not found in the platform directories: 'paths'.
|
|
Cause
| The platform library 'libSource' was not found in the platform directories: 'paths'.
|
|
Action
| Ensure the platform library is available in one of the specified directories. Or specify the correct directory during server startup.
|
|
|
BEA-149177(retired)
|
Warning: The platform library file 'libSource' is not in the correct location and will not be deployed.
|
Description
| The platform library file 'libSource' is not in the correct location and will not be deployed.
|
|
Cause
| The platform library file 'libSource' is not in the correct location and will not be deployed.
|
|
Action
| Ensure the platform library is available in a subdirectory of the platform library directories location.
|
|
|
BEA-149178
|
Warning: Application 'app' is targeted to cluster 'cluster' and provided target for operation operation is 'target'. This can potentially lead to client request problems on the cluster.
|
Description
| Application 'app' is targeted to cluster 'cluster' and provided target for operation operation is 'target'. This can potentially lead to client request problems on the cluster.
|
|
Cause
| This is a warning for an operation performed on a subset of a cluster for an application targeted to the cluster.
|
|
Action
| Ensure the cluster properly serves requests by performing operations on the cluster rather then individual servers in the cluster.
|
|
|
BEA-149179(retired)
|
Warning: The platform library, 'app', with version 'newVersion' cannot be deployed from 'path'. The application/library was previously deployed without version from 'configuredPath'.
|
Description
| The platform library, 'app', with version 'newVersion' cannot be deployed from 'path'. The application/library was previously deployed without version from 'configuredPath'.
|
|
Cause
| An attempt was made to deploy a versioned library when it was previously deployed without version.
|
|
Action
| Try reconfiguring the library(s) specified with correct version.
|
|
|
BEA-149180(retired)
|
Warning: The platform library 'app' cannot be deployed without version from 'path'. The application/library was previously deployed with version 'oldVersion' from 'configuredPath'.
|
Description
| The platform library 'app' cannot be deployed without version from 'path'. The application/library was previously deployed with version 'oldVersion' from 'configuredPath'.
|
|
Cause
| An attempt was made to deploy a library without version when it was previously deployed with version.
|
|
Action
| Try reconfiguring the library(s) specified with correct version.
|
|
|
BEA-149181
|
Error: Deployment Service encountered error while aborting the edit session before start. Initiator for this edit session is 'initiator'. Error is 't'
|
Description
| Deployment Service encountered error while aborting the edit session before start. Initiator for this edit session is 'initiator'. Error is 't'
|
|
Cause
| unkown
|
|
Action
| unkown
|
|
|
BEA-149182
|
Error: Invalid alternate descriptor specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
|
Description
| Invalid alternate descriptor specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
|
|
Cause
| Invalid alternate descriptor specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
|
|
Action
| Repeat the redeploy operation without the alternate descriptor.
|
|
|
BEA-149183
|
Error: Invalid retiretimeout option specified for deploy operation. Retiretimeout option was specified as 'retiretimeout' for the initial deployment of application 'name'. Retirement policies must be set during the deploy/redeploy of the next version in order to apply to version 'version' of 'name'.
|
Description
| The option is invalid for a deploy operation.
|
|
Cause
| Invalid retiretimeout option specified for deploy operation.
|
|
Action
| Specify the retiretimeout option during the deploy/redeploy of subsequent versions in order to have the retirement happen correctly at that time.
|
|
|
BEA-149184
|
Error: The application 'name' was autodeployed and may only be redeployed by touching REDEPLOY file in the domain autodeploy directory for respected application.
|
Description
| The application 'name' was autodeployed and may only be redeployed by touching REDEPLOY file in the domain autodeploy directory for respected application.
|
|
Cause
| Autodeployed application cannot be redeployed through tools.
|
|
Action
| Look at the documentation on autodeployed applications.
|
|
|
BEA-149185
|
Error: The application 'name' was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.
|
Description
| The application 'name' was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.
|
|
Cause
| Autodeployed application cannot be undeployed through tools.
|
|
Action
| Look at the documentation on autodeployed applications.
|
|
|
BEA-149186
|
Error: The application 'name' was autodeployed and cannot be redistributed.
|
Description
| The application 'name' was autodeployed and cannot be redistributed.
|
|
Cause
| Autodeployed application cannot be redistributed.
|
|
Action
| Look at the documentation on autodeployed applications.
|
|
|
BEA-149187
|
Warning: An unexpected error specifying configuration information for the application 'appName' due to t.
|
Description
| An unexpected error specifying configuration information for the application 'appName' due to t.
|
|
Cause
| Application configuration upgrade requires targeting information.
|
|
Action
| Inspect problematic application parts and deploy application.
|
|
|
BEA-149188
|
Warning: No application named 'app' exists for operation method. Operation can not be performed until server is restarted.
|
Description
| Unable to perform the method request for application 'app', since it does not exist. If a non-dynamic change is made to the configuration, then the server must be restarted before configuration changes can be applied. The application will not exist until the server is restarted.
|
|
Cause
| The application was created after non-dynamic changes were activated and the server needed to be restarted.
|
|
Action
| Restart the server and then start the application. In the future, start the application before making non-dynamic changes to the configuration.
|
|
|
BEA-149189
|
Warning: Attempt to operate 'operation' on null BasicDeploymentMBean for deployment deploymentName. Operation can not be performed until server is restarted.
|
Description
| Unable to perform the 'operation' operation for application deploymentName, since it does not exist. If a non-dynamic change is made to the configuration, then the server must be restarted before configuration changes can be applied. The application will not exist until the server is restarted.
|
|
Cause
| The application may have been created after non-dynamic changes were activated and the server needed to be restarted.
|
|
Action
| Restart the server and then perform the operation on the application.
|
|
|
BEA-149190
|
Warning: Changes are pending from another session whose lock has expired. This deployment operation will not activate changes from another edit session and hence cannot proceed. Either cancel the edit lock or activate the pending changes using the console or WLST.
|
Description
| During an edit session, a user has made changes. However, the edit session lock has expired, and the current deployment operation will not activate changes from another edit session.
|
|
Cause
| Changes were made with an edit session that has now expired.
|
|
Action
| Cancel the edit lock or activate the pending changes using the console or WLST.
|
|
