|
BEA-260000
|
Info: WebLogic Local Deployment Manager
|
Description
| Display name |
|
Cause
| None |
|
Action
| None |
|
|
BEA-260001
|
Error: 'uri' does not identify a known Deployment Manager. The URI must be of the form: deployer:WebLogic:host:port. The host and port are required if attempting to acquire a connected deployment manager.
|
Description
| The URI must be of the form: deployer:WebLogic:host:port. The host and port are required if attempting to acquire a connected deployment manager. |
|
Cause
| Invalid URI provided when allocating a deployment manager |
|
Action
| None required |
|
|
BEA-260002
|
Error: 'uri' is not a valid uri. The URI must be of the form: "deployer:WebLogic:protocol://host:port". The host and port are required if attempting to acquire a connected deployment manager. The protocol should be a well-known IP protocol.
|
Description
| The URI must be of the form: "deployer:WebLogic:protocol://host:port". The host and port are required if attempting to acquire a connected deployment manager. |
|
Cause
| Incorrect host/port used when attempting to allocate a deployment manager. |
|
Action
| None |
|
|
BEA-260003
|
Error: Feature not available when in disconnected mode.
|
Description
| Certain deployment operation require a connected deployment manager |
|
Cause
| Deployment tool allocated a disconnected deployment manager or released it. |
|
Action
| Allocate a connected deployment manager. |
|
|
BEA-260004
|
Error: Locale, 'locale', is not supported.
|
Description
| The specified locale is not supported by this JVM |
|
Cause
| Locale is incorrectly specified |
|
Action
| None |
|
|
BEA-260005(retired)
|
Info: WebLogic Server
|
Description
| Display name |
|
Cause
| None |
|
Action
| None |
|
|
BEA-260006(retired)
|
Info: WebLogic Cluster
|
Description
| Display name |
|
Cause
| None |
|
Action
| None |
|
|
BEA-260007(retired)
|
Info: WebLogic Virtual Host
|
Description
| Display name |
|
Cause
| None |
|
Action
| None |
|
|
BEA-260008
|
Error: J2EE version v not supported by this deployment manager.
|
Description
| Only J2EE 1.4 and later versions are supported. |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260009
|
Error: Exception caught for class 'cls' while attempting to create DeploymentManager: err
|
Description
| Internal error |
|
Cause
| Internal error |
|
Action
| None |
|
|
BEA-260010
|
Error: Unable to connect to 'url' as user, 'user'. Error received: msg
|
Description
| Unable to create connect deployment manager |
|
Cause
| Failed authorization |
|
Action
| None |
|
|
BEA-260011(retired)
|
Error: Unable to create unique id for module [ domain: 'domain',name: 'name',type: 'type',target: 'target',target type: 'targetType', parent application: 'app' ]. Reported err was: msg
|
Description
| Internal error |
|
Cause
| Internal error |
|
Action
| None |
|
|
BEA-260012
|
Error: No configured targets match provided target with name, 'target', and type, 'type'
|
Description
| Attempt to deploy to unknown target |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260013
|
Error: Target array passed to DeploymentManager was null or empty.
|
Description
| Invalid argument |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260014(retired)
|
Error: Client applications not supported
|
Description
| Operation not supported for client applications |
|
Cause
| Invalid request |
|
Action
| None |
|
|
BEA-260015
|
Error: The 'op' operation is not supported
|
Description
| Unsupported operation |
|
Cause
| Invalid request |
|
Action
| None |
|
|
BEA-260016
|
Error: 'file' does not exist.
|
Description
| Attempted to create deployable object with invalid module path |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260017
|
Error: Unable to locate deployment task, 'task'
|
Description
| A deployment task cannot be found. No further updates will be provided to the associated ProgressObject |
|
Cause
| Task was removed from the system |
|
Action
| None |
|
|
BEA-260018(retired)
|
Error: Failed to create cmd task using object.
|
Description
| A management error occurred while creating a deployment task |
|
Cause
| Check log for further details |
|
Action
| None |
|
|
BEA-260019(retired)
|
Info: Module mod of application app is transitioning from start to target on server server.
|
Description
| State transition |
|
|
BEA-260020
|
Info: Module mod of application app successfully transitioned from start to target on server server.
|
Description
| State transition |
|
|
BEA-260021
|
Info: Module mod of application app failed to transition from start to target on server server.
|
Description
| State transition |
|
|
BEA-260022
|
Info: phase application app on server server.
|
Description
| State transition |
|
|
BEA-260023
|
Warning: Deployment task does not exist for ProgressObject
|
Description
| No further updates will be made to ProgressObject |
|
Cause
| Deployment task was removed from system |
|
Action
| None |
|
|
BEA-260024
|
Info: Connection errors occurred while reporting a progress event. The event was from application, app, module, mod, on server server. The event was msg. The error was err.
|
Description
| Progress report |
|
Cause
| Deployment failure |
|
Action
| None |
|
|
BEA-260025(retired)
|
Error: No modules configured on targets.
|
Description
| A distribute operation resulted in no application being configured |
|
Cause
| Check log for further details |
|
Action
| None |
|
|
BEA-260026
|
Error: Task failed for unknown reason. Task description is task
|
Description
| Task failed but without exceptions |
|
Cause
| Unknown |
|
Action
| None |
|
|
BEA-260027
|
Error: Non-root module, 'tmid', is not supported for op operations. All modules must represent root modules.
|
Description
| All modules must represent root modules. The operation does not support embedded modules. |
|
Cause
| Unsupported operation |
|
Action
| Use DeploymentManager.enableModuleTargeting |
|
|
BEA-260028
|
Error: No targeting information provided for op operation.
|
Description
| The operation requires something to deploy and targeting information. |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260029
|
Error: 'tmid' is not part of application, 'app'. Only one application allowed for op operation.
|
Description
| Multiple applications may not be specified in the same operation |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260030
|
Error: Module, 'tmid', is not part of any application.
|
Description
| Application is not configured |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260031
|
Info: No action performed or required for cmd request.
|
Description
| All specified modules are already in the necessary state. |
|
Cause
| None |
|
Action
| None |
|
|
BEA-260032(retired)
|
Error: Unable to perform cmd operation. At least one module, 'mod', is still active.
|
Description
| Modules must be stopped before undeploying them. |
|
Cause
| Invalid request |
|
Action
| None |
|
|
BEA-260036
|
Error: Module type, 'type', not supported.
|
Description
| Operation not supported for specified module type |
|
Cause
| unsupported operation |
|
Action
| None |
|
|
BEA-260037
|
Error: Encountered unexpected descriptor for module 'archive'.
|
Description
| Descriptor for EAR describes a different module type. |
|
Cause
| Invalid application descriptor in EAR |
|
Action
| Fix application |
|
|
BEA-260038(retired)
|
Error: No archive or plan provided in cmd request.
|
Description
| Deployment operation needs an application and/or plan to deploy |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260040
|
Error: No files provided in cmd request.
|
Description
| Must specify at least one file for update. |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260041
|
Error: Unable to upload 'file' to 'url'
|
Description
| Files in request need to be uploaded to remote admin server |
|
Cause
| Check log for further details |
|
Action
| None |
|
|
BEA-260043(retired)
|
Error: Property 'prop' in element of type 'bean' with key, 'key', is missing or invalid
|
Description
| Missing information detected in app configuration. Deployment plan cannot be created until configuration problem is resolved. |
|
Cause
| Missing configuration information |
|
Action
| Modify app configuration. |
|
|
BEA-260047(retired)
|
Error: Multiple modules with same name, 'name', defined in application.
|
Description
| All embedded modules must have unique names |
|
Cause
| Invalid application |
|
Action
| Fix the application |
|
|
BEA-260049(retired)
|
Error: 'tag' is already registered as secondary descriptor
|
Description
| New registrations of descriptors are keyed off the main descriptor uri. |
|
Cause
| The uri used to register the descriptor is already in use. |
|
Action
| None |
|
|
BEA-260050
|
Error: 'classname' does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: msg.
|
Description
| Internal error |
|
Cause
| Internal error |
|
Action
| None |
|
|
BEA-260052
|
Error: null DConfigBeanRoot.
|
Description
| Invalid argument |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260053(retired)
|
Error: DConfigBeanRoot not in configuration.
|
Description
| Invalid argument |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260055
|
Error: Unable to parse deployment plan: 'msg'
|
Description
| Could not read or parse plan during deployment operation |
|
Cause
| The document is invalid |
|
Action
| None |
|
|
BEA-260056
|
Error: MBean must be for Application or Component: 'oname'
|
Description
| Invalid argument |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260057(retired)
|
Error: argname argument cannot be null.
|
Description
| Invalid argument |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260060(retired)
|
Error: 'plan' is not a deployment plan.
|
Description
| Invalid plan document specified in request |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260061
|
Error: Unable to recognize DDBean with xpath, 'xpath'.
|
Description
| Unable to restore configuration from invalid descriptor |
|
Cause
| Invalid argument |
|
Action
| None |
|
|
BEA-260062(retired)
|
Error: Failed cmd operation: msg
|
Description
| A deployment operation failed. |
|
Cause
| Error encountered during deployment. |
|
Action
| Depends on specific error. |
|
|
BEA-260063(retired)
|
Error: Failed cmd operation: msg
|
Description
| A deployment operation failed. |
|
Cause
| Error encountered during deployment. |
|
Action
| Depends on specific error. |
|
|
BEA-260064(retired)
|
Info: cmd operation completed successfully.
|
Description
| A deployment operation was successful |
|
|
BEA-260065(retired)
|
Info: Connection released during running cmd operation.
|
Description
| The deployment operation will continue but no further status will be reported. |
|
Cause
| The deployment tool released the its deployment manager. |
|
Action
| None required. |
|
|
BEA-260066(retired)
|
Error: Unable to read 'arc': msg
|
Description
| Unable to enumerate archive entries due to IOException |
|
Cause
| IO Failures |
|
Action
| None |
|
|
BEA-260067
|
Info: Restored configuration for module, mod
|
Description
| The in-memory configuration for a module was updated on request. |
|
Cause
| DeploymentConfiguration.restoreDConfigBean was invoked |
|
|
BEA-260068
|
Info: Removed configuration for module, mod
|
Description
| The in-memory configuration for a module was deleted on request. |
|
Cause
| DeploymentConfiguration.removeDConfigBean was invoked |
|
|
BEA-260070
|
Info: Saved configuration for module, mod
|
Description
| The in-memory configuration for a module was written to disk |
|
Cause
| DeploymentConfiguration.saveDConfigBean was invoked |
|
|
BEA-260071
|
Info: Restored configuration for application, app
|
Description
| The in-memory configuration for an application was updated on request. |
|
Cause
| DeploymentConfiguration.restore was invoked |
|
|
BEA-260072
|
Info: Saved configuration for application, app
|
Description
| The in-memory configuration for an application was written to disk |
|
Cause
| DeploymentConfiguration.save was invoked |
|
|
BEA-260073
|
Error: Unable to introspect on bean, 'clazz'
|
Description
| An Intropsection exception occurred while determining a beans key value. |
|
Cause
| Internal error |
|
Action
| None required |
|
|
BEA-260074(retired)
|
Warning: The configuration for module 'name' is being read from application archive. Resulting plan will not include the configuration for this module.
|
Description
| If a module configuration already exists in the archive then it will not be part of the deployment plan. Any changes made to the configuration will not be included when the plan is saved. |
|
Cause
| Module is already configured. |
|
Action
| Configuration changes for this module must be made to the embedded configuration or via variable declarations. |
|
|
BEA-260075(retired)
|
Warning: The configuration for module 'name' cannot be saved in deployment plan.
|
Description
| If a module configuration already exists in the archive then it will not be part of the deployment plan. Any changes made to the configuration will not be included when the plan is saved. |
|
Cause
| Module is already configured. |
|
Action
| Configuration changes for this module must be made to the embedded configuration or via variable declarations. |
|
|
BEA-260076(retired)
|
Warning: The configuration for module 'name' is defined using an unsupported, DTD-based, descriptor.
|
Description
| The descriptor for this module will not be represented in the configuration. |
|
Cause
| Module uses unsupported descriptor version. |
|
Action
| Update the descriptor to the most current release level. |
|
|
BEA-260077(retired)
|
Warning: An exception occurred while parsing descriptor for module 'name' at 'uri': msg.
|
Description
| IO failures were detected or the descriptor is invalid. |
|
Cause
| Check error message for specific problem. |
|
Action
| None required. |
|
|
BEA-260078
|
Warning: No DConfigBean is available for invalid module, 'uri': msg.
|
Description
| A ConfigurationException was thrown while processing a descriptor. |
|
Cause
| Check error message for specific problem. |
|
Action
| None required. |
|
|
BEA-260079(retired)
|
Error: Unable to explode embedded archive, 'file'
|
Description
| The application contains embedded archives which need to be exploded to access all descriptors. |
|
Cause
| Sharing violation. |
|
Action
| None required. |
|
|
BEA-260080
|
Error: Unable to define application install directory at 'file'. Directory could not be created or is a file.
|
Description
| The indicated directory must be available or use during the configuration process. |
|
Cause
| Directory could not be created or is a file. |
|
Action
| Specify a valid directory |
|
|
BEA-260081
|
Error: The descriptor at 'file' could not be parsed.
|
Description
| The descriptor contains syntax errors |
|
Cause
| The descriptor is invalid |
|
Action
| None |
|
|
BEA-260082
|
Warning: A required descriptor, file, for a CMP bean is missing.
|
Description
| The descriptor is referred to by the EJB deployment configuration descriptor but is not available in the archive or the configuration directory. |
|
Cause
| Missing descriptor file |
|
Action
| Place the necessary descriptor in the archive or its external configuration area |
|
|
BEA-260083
|
Warning: No plan document at 'file'
|
Description
| The plan document specified for input to a configuration session does not exist. Processing will continue without an input plan. |
|
Cause
| The path for the plan may have been incorrectly specified. If this is the first time the application is being configured this may not be a problem; the plan will be created. |
|
Action
| Specify correct plan location as necessary. |
|
|
BEA-260084(retired)
|
Info: Deployment descriptors in app are not schema based.
|
|
BEA-260085
|
Warning: The configuration descriptor for 'module' already exists ( internal ), or wasn't modified ( modified ), and won't be saved.
|
Description
| When saving a configuration, one or more descriptor files are written to the configuration area only if those files do not preexist and were modified during the configuration session. If modifications were made, they are represented by variable assignments in the saved plan document. |
|
Cause
| The descriptors don't need to be saved. |
|
Action
| None required |
|
|
BEA-260086
|
Info: The descriptor information at uri was saved to configuration area.
|
Description
| When saving a configuration, one or more descriptor files are written to the configuration area only if those files do not already exist. |
|
Cause
| The configuration was saved |
|
Action
| None required |
|
|
BEA-260087
|
Error: The descriptor at 'dd' is missing the required element element for custom module with uri, 'uri', and provider, 'prov'
|
Description
| The weblogic-extensions.xml descriptor was found in the application and is missing some required elements. |
|
Cause
| The named element is missing. |
|
Action
| Correct errors in weblogic-extensions.xml descriptor. |
|
|
BEA-260088
|
Error: The type descriptor at 'dd' is missing.
|
Description
| The weblogic-application descriptor references a JMS/JDBC descriptor. |
|
Cause
| The JMS/JDBC descriptor is not present in the archive. |
|
Action
| Ensure all descriptors are in place. |
|
|
BEA-260089(retired)
|
Error: Unable to determine type of application at path 'app'.
|
Description
| Application must be a supported type. |
|
Cause
| The file is not a valid application. |
|
Action
| None Required. |
|
|
BEA-260090(retired)
|
Error: Attempt to construct DeployableObject for EAR, 'app'
|
Description
| WebLogicDeployableObject describes a standalone module. WebLogicJ2eeApplicationObject should be used for EARs. |
|
Cause
| Wrong constructor used. |
|
Action
| Use WebLogicJ2eeApplicationObject to describe EARs. |
|
|
BEA-260091
|
Error: Errors detected when reading 'app': msg
|
Description
| The application was being inspected for module type information. |
|
Cause
| Depends on error in message |
|
Action
| None required. |
|
|
BEA-260092(retired)
|
Error: Module type, 'type1', specified for 'app' doesn't match actual module type, type2
|
Description
| The actual module type can be determined from the applications structure |
|
Cause
| Wrong type or application specified. |
|
Action
| Dont specify module type; let system derive from application structure. |
|
|
BEA-260093(retired)
|
Error: Unable to set module type for 'module'.
|
Description
| A TargetInfoMBean for the module must have its module type set up. |
|
Cause
| Module type information cannot be derived from information in the provided plan or by inspecting the application archive. |
|
Action
| Provide a valid plan when distributing the application. |
|
|
BEA-260094
|
Info: Registering config module descriptor support with base uri, base, and config uri, config.
|
Description
| Config module descriptors are registered via the weblogic-extensions descriptor. |
|
Cause
| The weblogic-extensions descriptor specified custom configuration descriptor support |
|
Action
| None required. |
|
|
BEA-260095
|
Error: Unable to create archive for 'app'
|
Description
| The input stream provided for a deployment operation must be written to a properly named file prior to proceeding |
|
Cause
| The attempt to name the file with the appropriate extension failed |
|
Action
| None required |
|
|
BEA-260096
|
Error: Unable to determine type of application for 'app'
|
Description
| The input stream provided for a deployment operation must be written to a properly named file prior to proceeding. The extension of the file must be established based on module type. |
|
Cause
| The archive does not contain standard descriptors. |
|
Action
| Ensure correct file was passed into the deployment operation. |
|
|
BEA-260097
|
Error: Unable to understand DDBeanRoot provided by deployer tool: 'bean'.
|
Description
| The DDBeanRoot object must have '/' as its xpath |
|
Cause
| The model API is not providing expected information |
|
Action
| Resolve API problems in class implementing javax.enterprise.deploy.model.DDBeanRoot |
|
|
BEA-260098
|
Error: No descriptor type is registered for modules of type, type
|
Description
| Descriptors are registered based on module type |
|
Cause
| The module type is not registered with a configurable descriptor |
|
Action
| Register non-standard descriptors using the weblogic-extension.xml descriptor. |
|
|
BEA-260099
|
Error: No root element in type descriptor, filename at uri.
|
Description
| Root elements must exist in deployment descriptor |
|
Cause
| Invalid descriptor provided for module |
|
Action
| Either wrong descriptor specified or module type is incorrect |
|
|
BEA-260100
|
Error: Invalid Value for Security Model, model. Should be one of models.
|
Description
| Message indicates valid values for security model. |
|
Cause
| An unrecognized security model was requested. |
|
Action
| Use a valid security model |
|
|
BEA-260101
|
Error: Parameter 'paramName' may not be null.
|
Description
| Misuse of an API |
|
Cause
| A null parameter was passed to the method. |
|
Action
| Resolve client programming error |
|
|
BEA-260102
|
Error: Type parameter, 'type', provided to export method is invalid
|
Description
| The valid types are defined in weblogic.deploy.api.spi.WebLogicDConfigBeanRoot |
|
Cause
| Invalid argument |
|
Action
| Use a valid export type |
|
|
BEA-260103
|
Error: The bean provided is not part of this configuration: 'bean'
|
Description
| The export(DescriptorBean,String[]) method must be applied on the relevant DConfigBeanRoot object. |
|
Cause
| An attempt was made to export bean properties against the wrong DConfigBeanRoot object |
|
Action
| Invoke export on the correct DConfigBeanRoot |
|
|
BEA-260104
|
Error: prop is not a changable property
|
Description
| The export(DescriptorBean,String[]) method can only be applied to changable properties |
|
Cause
| One of the properties is not changable |
|
Action
| Remove property from list |
|
|
BEA-260105(retired)
|
Error: Failed to create DDBeanRoot for application, 'arc'.
|
Description
| DDBeanRoot objects are created from standard descriptors in the application. |
|
Cause
| Unable to access or parse descriptor for module. |
|
Action
| Ensure application is accessible and contains valid descriptors. |
|
|
BEA-260106
|
Error: Failed to parse descriptor at 'uri' for module 'arc': msg
|
Description
| The WebLogic descriptor for the module cannot be parsed. |
|
Cause
| The descriptor is not valid |
|
Action
| Ensure application is accessible and contains valid descriptors. |
|
|
BEA-260107
|
Error: Failed to write descriptor for module 'name' configuration: msg.
|
Description
| WebLogic descriptors are written to disc as part of a save operation. |
|
Cause
| An IO error prevented the save operation or the descriptor is missing some required elements. |
|
Action
| Depends om specific error. |
|
|
BEA-260108
|
Error: Failed to restore descriptors: msg.
|
Description
| WebLogic descriptors are written to disk read and parsed as part of a restore operation. |
|
Cause
| An IO or parse error prevented the restore operation. |
|
Action
| Depends om specific error. |
|
|
BEA-260109
|
Error: Failed to write deployment plan: msg.
|
Description
| Deployment plans are written to disk as part of a save operation. |
|
Cause
| An IO error prevented the save operation or the plan is missing some required elements. |
|
Action
| Depends om specific error. |
|
|
BEA-260110
|
Error: Failed to create configuration for module: obj
|
Description
| Failures detected while constructing a DeploymentConfiguration object. |
|
Cause
| The configuration artifacts for the application could not be processed. This could result from simple access errors, descriptor parsing failures or basic application architecture problems. |
|
Action
| Depends om specific error. The configuration artifacts for the application could not be processed. This could result from simple access errors, descriptor parsing failures or basic application architecture problems. |
|
|
BEA-260111
|
Error: Errors detected attempting to communicate with admin server.
|
Description
| Deployment operations require a connection to the domain admin server. |
|
Cause
| Depends on the specific error. The associated exception will nest the root exception. |
|
Action
| Depends om specific error. |
|
|
BEA-260112
|
Error: Unable to determine application name from null or empty TargetModuleID list.
|
Description
| The deployment operation requires a list of TargetModuleID objects |
|
Cause
| No TargetModuleID objects were provided |
|
Action
| Resolve client programming error |
|
|
BEA-260113
|
Error: Plan at 'plan' is a directory. A deployment plan is always an XML document.
|
Description
| A deployment plan is always an XML document. |
|
Cause
| Plan at 'plan' is a directory. |
|
Action
| Resolve client programming error |
|
|
BEA-260114
|
Error: Application root at 'root' is not a directory.
|
Description
| Application roots are always directories |
|
Cause
| Invalid root directory specified. |
|
Action
| Resolve client programming error |
|
|
BEA-260115
|
Error: Must specify application to configure
|
Description
| An application must be specified in order to configure it. |
|
Cause
| No application specified |
|
Action
| Resolve client programming error |
|
|
BEA-260116
|
Error: Configuration is not initialized
|
Description
| Must initialize the application configuration before saving it |
|
Cause
| SessionHelper.initialize() not yet invoked |
|
Action
| Resolve client programming error |
|
|
BEA-260117
|
Error: Unable to load factory, 'factory'
|
Description
| Factory not in class path |
|
Cause
| Factory not in class path |
|
Action
| Ensure factory is in classpath |
|
|
BEA-260118
|
Error: A null target was included in a deployment request
|
Description
| Targets are validated prior to deployment |
|
Cause
| Invalid Target list |
|
Action
| Resolve client programming error |
|
|
BEA-260119
|
Error: The path provided, 'path', does not represent a directory
|
Description
| SessionHelper.savePlan(File dirname, String planName). First argument must be a directory. |
|
Cause
| User error |
|
Action
| Resolve client programming error |
|
|
BEA-260120(retired)
|
Error: Failed to create deployment manager for uri, 'uri', as user, 'uid': msg
|
Description
| An attempt to create a connected deployment manager was unsuccessful |
|
Cause
| The client could not establish a connection with the domain admin server |
|
Action
| Depends on specific error |
|
|
BEA-260121
|
Info: Initiating cmd operation for application, app [archive: arc], to targets.
|
Description
| Logged at start of a deployment operation. |
|
Cause
| Starting a deployment operation. |
|
Action
| none |
|
|
BEA-260122
|
Info: Initiating cmd operation for application, app, from stream to targets.
|
Description
| Logged at start of a deployment operation. |
|
Cause
| Starting a deployment operation. |
|
Action
| none |
|
|
BEA-260123
|
Info: Unable to determine targets for deployment request on application, app
|
Description
| No application with indicated name exists, and no targets were specified in the request. |
|
Cause
| No targets specified for new deployment |
|
Action
| Specify targets |
|
|
BEA-260124
|
Info: configured targets
|
Description
| Text when targets are unknown |
|
Cause
| No targets specified |
|
Action
| None required |
|
|
BEA-260125
|
Error: Errors detected attempting to communicate with admin server: msg
|
Description
| Deployment operations require a connection to the domain admin server. |
|
Cause
| Depends on the specific error. The associated exception will nest the root exception. |
|
Action
| Depends om specific error. |
|
|
BEA-260126
|
Error: Cannot override plan version, 'v1', with version from options, 'v2'.
|
Description
| Version information specified in the plan document cannot be overridden |
|
Cause
| A plan version was specified in the deployment options, but the plan defines its own version. |
|
Action
| Do not specify version |
|
|
BEA-260127(retired)
|
Error: Cannot override application version, 'v1', with version from options, 'v2'.
|
Description
| Version information specified in the application archive cannot be overridden |
|
Cause
| An application version was specified in the deployment options, but the application defines its own version. |
|
Action
| Do not specify version |
|
|
BEA-260128
|
Warning: Changes not allowed to DTD based descriptors. The attempt to modify property 'prop' in dd for module 'mod' will be vetoed if possible. The change will not be persisted in either case.
|
Description
| Deployment plans do not support DTD-based descriptors. |
|
Cause
| A property in a DTD based descriptor was modified. |
|
Action
| Upgrade the application with schema based descriptors. |
|
|
BEA-260129
|
Warning: Export not allowed on DTD based descriptors. No properties for the dd descriptor in module, 'mod', will be exported.
|
Description
| Deployment plans do not support DTD-based descriptors. |
|
Cause
| Attempted to export a DTD based descriptor |
|
Action
| Upgrade the application with schema based descriptors. |
|
|
BEA-260130
|
Warning: Shutting down DeploymentManager connection due to internal error
|
Description
| The connection can no longer be used. All active ProgressObjects will be set to RELEASED state. |
|
Cause
| An internal error occurred |
|
Action
| Allocate a new DeploymentManager |
|
|
BEA-260131
|
Error: No URI provided.
|
Description
| No URI provided. |
|
Cause
| Attempted to create a deployment manager without providing an appropriate deployer uri. |
|
Action
| Provide a deployer uri. |
|
|
BEA-260132
|
Error: 'name1' is not a child of 'name2'.
|
Description
| 'name1' is not a child of 'name2'. |
|
Cause
| 'name1' is not a child of 'name2'. |
|
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 Oracle Customer Support and provide the stack trace for further analysis. |
|
|
BEA-260133
|
Error: The descriptor at 'file' could not be parsed due to error: msg.
|
Description
| The named descriptor is invalid. |
|
Cause
| The descriptor is invalid |
|
Action
| None |
|
|
BEA-260134
|
Error: Unable to identify application for op operation.
|
Description
| The app name is derived from information present in the operation's arguments, including the archive, plan, DEploymentOptions and TargetModuleID's. |
|
Cause
| Insufficient information was provided to identify the application to deploy. |
|
Action
| Resolve client programming error. |
|
|
BEA-260135(retired)
|
Error: Unable to identify application for cmd operation from null or empty TargetModuleID list.
|
Description
| The deployment operation requires a list of TargetModuleID objects |
|
Cause
| No TargetModuleID objects were provided |
|
Action
| Resolve client programming error |
|
|
BEA-260136(retired)
|
Warning: Failures were detected while merging libraries: msg. Session will not include referenced libraries.
|
Description
| The application references one or more libraries. These should be imported into the configuration session to obtain a complete view of the application. |
|
Cause
| The application has library references which could not be merged into the application. |
|
Action
| Ensure referenced libraries are available |
|
|
BEA-260137
|
Warning: Failures were detected while restoring original plan file msg. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan 'backupPlan'.
|
Description
| Failures were detected while restoring original plan file msg. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan 'backupPlan'. |
|
Cause
| Failures were detected while restoring original plan file msg. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan 'backupPlan'. |
|
Action
| Either attempt to update the application again with the current plan, or make use of the backup plan 'backupPlan'. |
|
|
BEA-260138
|
Warning: Failures were detected while trying to create a backup plan.xml file at 'planBackup' msg.
|
Description
| Failures were detected while trying to create a backup plan.xml file at 'planBackup' msg. |
|
Cause
| Failures were detected while trying to create a backup plan.xml file at 'planBackup' msg. |
|
Action
| Failures were detected while trying to create a backup plan.xml file at 'planBackup' msg. |
|
|
BEA-260139
|
Info: Unchanged plan.xml was restored due to problems updating new plan msg.
|
Description
| Unchanged plan.xml was restored due to problems updating new plan msg. |
|
Cause
| Unchanged plan.xml was restored due to problems updating new plan msg. |
|
Action
| Unchanged plan.xml was restored due to problems updating new plan msg. |
|
|
BEA-260140
|
Info: Unable to remove descriptor bean name due to 'msg'. The remover should first check to see if the bean is removable in the deployment plan prior to removing it.
|
Description
| Unable to remove descriptor bean name due to msg. The remover should first check to see if the bean is removable in the deployment plan prior to removing it. |
|
Cause
| Unable to remove descriptor bean name due to msg. The remover should first check to see if the bean is removable in the deployment plan prior to removing it. |
|
Action
| Unable to remove descriptor bean name due to msg. The remover should first check to see if the bean is removable in the deployment plan prior to removing it. |
|
|
BEA-260141
|
Error: An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().
|
Description
| An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close(). Call close() on the SessionHelper instance, and avoid reusing the same instance. |
|
Cause
| An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close(). |
|
Action
| An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close(). Call close() on the SessionHelper instance, and avoid reusing the same instance. |
|
|
BEA-260142
|
Error: The descriptor at 'file' in module 'module' is not recognized, and could not be parsed.
|
Description
| The descriptor is unknown. |
|
Cause
| The descriptor is unknown. |
|
Action
| None. |
|
