The Deployer1.0 catalog contains messages in the range
BEA149000 - BEA149199. Messages in this catalog are part of the
weblogic.management.deploy.internal
Internationalization package and the weblogic.i18n Localization package.
|
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 mispelled. |
|
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 depoyed. |
|
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
|
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
|
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
|
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. Re-specify the source to deploy additional modules for an application. validModuleNames are the valid module(s) for this application.
|
Description
| An attempt to activate 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
|
Warning: Unable to remove target from component comp.
|
Description
| A request to deactivate a component on a server, cluster, or virtual host could not be completed. |
|
Cause
| The component 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
|
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
|
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
|
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
|
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
|
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
|
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: A deployment task with ID id for application appName is being initiated.
|
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
|
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
|
Error: An attempt to add cluster target cluster to module module has been made, 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
|
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 aso 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
Debug: 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
|
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
|
Warning: Application, app, does not define the module, module. validModuleNames is (are) the valid module(s) for this application.
|
Description
| An attempt to perform deployment operation with undefined module was rejected |
|
Cause
| Incorrect deployment information provided in the deployment operation request. |
|
Action
| Ensure that the module information in the request is accurate. |
|
|
BEA-149099
|
Warning: Application app is not deployed on target target. Hence it cannot be Redeployed / 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 Redeployed / 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-149100
|
Error: Unable to delete file file
|
Description
| Unable to delete file file |
|
Cause
| Unable to delete file file |
|
Action
| Manually delete file file. |
|
