《weblogic布署时,出现错误代码对应的错误信息.doc》由会员分享，可在线阅读，更多相关《weblogic布署时,出现错误代码对应的错误信息.doc（16页珍藏版）》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。
1、J2EE Deployment SPI Subsystem MessagesThe J2EE Deployment SPI1.0 catalog contains messages in the range BEA - BEA. Messages in this catalog are part of the weblogic.deploy.api.internal Internationalization package and the weblogic.deploy.api.internal Localization package.BEA- Info: WebLogic Local De
2、ployment ManagerDescription Display nameCause NoneAction NoneBEA- 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 t
3、he 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 managerAction None requiredBEA- Error: uri is not a valid uri. The URI must be of the form: deployer:WebLogic:protocol:
4、/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 depl
5、oyment manager.Cause Incorrect host/port used when attempting to allocate a deployment manager.Action NoneBEA- Error: Feature not available when in disconnected mode.Description Certain deployment operation require a connected deployment managerCause Deployment tool allocated a disconnected deployme
6、nt manager or released it.Action Allocate a connected deployment manager.BEA- Error: Locale, locale, is not supported.Description The specified locale is not supported by this JVMCause Locale is incorrectly specifiedAction NoneBEA-(retired) Info: WebLogic ServerDescription Display nameCause NoneActi
7、on NoneBEA-(retired) Info: WebLogic ClusterDescription Display nameCause NoneAction NoneBEA-(retired) Info: WebLogic Virtual HostDescription Display nameCause NoneAction NoneBEA- Error: J2EE version v not supported by this deployment manager.Description Only J2EE 1.4 and later versions are supported
8、.Cause Invalid argumentAction NoneBEA- Error: Exception caught for class cls while attempting to create DeploymentManager: errDescription Internal errorCause Internal errorAction NoneBEA- Error: Unable to connect to url as user, user. Error received: msgDescription Unable to create connect deploymen
9、t managerCause Failed authorizationAction NoneBEA-(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: msgDescription Internal errorCause Internal errorAction NoneBEA- Error: No
10、 configured targets match provided target with name, target, and type, typeDescription Attempt to deploy to unknown targetCause Invalid argumentAction NoneBEA- Error: Target array passed to DeploymentManager was null or empty.Description Invalid argumentCause Invalid argumentAction NoneBEA-(retired)
11、 Error: Client applications not supportedDescription Operation not supported for client applicationsCause Invalid requestAction NoneBEA- Error: The op operation is not supportedDescription Unsupported operationCause Invalid requestAction NoneBEA- Error: file does not exist.Description Attempted to c
12、reate deployable object with invalid module pathCause Invalid argumentAction NoneBEA- Error: Unable to locate deployment task, taskDescription A deployment task cannot be found. No further updates will be provided to the associated ProgressObjectCause Task was removed from the systemAction NoneBEA-(
13、retired) Error: Failed to create cmd task using object.Description A management error occurred while creating a deployment taskCause Check log for further detailsAction NoneBEA-(retired) Info: Module mod of application app is transitioning from start to target on server server.Description State tran
14、sitionBEA- Info: Module mod of application app successfully transitioned from start to target on server server.Description State transitionBEA- Info: Module mod of application app failed to transition from start to target on server server.Description State transitionBEA- Info: phase application app
15、on server server.Description State transitionBEA- Warning: Deployment task does not exist for ProgressObjectDescription No further updates will be made to ProgressObjectCause Deployment task was removed from systemAction NoneBEA- Info: Connection errors occurred while reporting a progress event. The
16、 event was from application, app, module, mod, on server server. The event was msg. The error was err.Description Progress reportCause Deployment failureAction NoneBEA-(retired) Error: No modules configured on targets.Description A distribute operation resulted in no application being configuredCaus
17、e Check log for further detailsAction NoneBEA- Error: Task failed for unknown reason. Task description is taskDescription Task failed but without exceptionsCause UnknownAction NoneBEA- Error: Non-root module, tmid, is not supported for op operations. All modules must represent root modules.Descripti
18、on All modules must represent root modules. The operation does not support embedded modules.Cause Unsupported operationAction Use DeploymentManager.enableModuleTargetingBEA- Error: No targetting information provided for op operation.Description The operation requires something to deploy and targetti
19、ng information.Cause Invalid argumentAction NoneBEA- 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 operationCause Invalid argumentAction NoneBEA- Error: Module, tmid, is not part of any ap
20、plication.Description Application is not configuredCause Invalid argumentAction NoneBEA- Info: No action performed or required for cmd request.Description All specified modules are already in the necessary state.Cause NoneAction NoneBEA-(retired) Error: Unable to perform cmd operation. At least one
21、module, mod, is still active.Description Modules must be stopped before undeploying them.Cause Invalid requestAction NoneBEA- Error: Module type, type, not supported.Description Operation not supported for specified module typeCause unsupported operationAction NoneBEA- Error: Encountered unexpected
22、descriptor for module archive.Description Descriptor for EAR describes a different module type.Cause Invalid application descriptor in EARAction Fix applicationBEA-(retired) Error: No archive or plan provided in cmd request.Description Deployment operation needs an application and/or plan to deployC
23、ause Invalid argumentAction NoneBEA- Error: No files provided in cmd request.Description Must specify at least one file for update.Cause Invalid argumentAction NoneBEA- Error: Unable to upload file to urlDescription Files in request need to be uploaded to remote admin serverCause Check log for furth
24、er detailsAction NoneBEA-(retired) Error: Property prop in element of type bean with key, key, is missing or invalidDescription Missing information detected in app configuration. Deployment plan cannot be created until configuration problem is resolved.Cause Missing configuration informationAction M
25、odify app configuration.BEA-(retired) Error: Multiple modules with same name, name, defined in application.Description All embedded modules must have unique namesCause Invalid applicationAction Fix the applicationBEA-(retired) Error: tag is already registered as secondary descriptorDescription New r
26、egistrations of descriptors are keyed off the main descriptor uri.Cause The uri used to register the descriptor is already in use.Action NoneBEA- Error: classname does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: msg.Description Internal errorCause Intern
27、al errorAction NoneBEA- Error: null DConfigBeanRoot.Description Invalid argumentCause Invalid argumentAction NoneBEA-(retired) Error: DConfigBeanRoot not in configuration.Description Invalid argumentCause Invalid argumentAction NoneBEA- Error: Unable to parse deployment plan: msgDescription Could no
28、t read or parse plan during deployment operationCause The document is invalidAction NoneBEA- Error: MBean must be for Application or Component: onameDescription Invalid argumentCause Invalid argumentAction NoneBEA-(retired) Error: argname argument cannot be null.Description Invalid argumentCause Inv
29、alid argumentAction NoneBEA-(retired) Error: plan is not a deployment plan.Description Invalid plan document specified in requestCause Invalid argumentAction NoneBEA- Error: Unable to recognize DDBean with xpath, xpath.Description Unable to restore configuration from invalid descriptorCause Invalid
30、argumentAction NoneBEA-(retired) Error: Failed cmd operation: msgDescription A deployment operation failed.Cause Error encountered during deployment.Action Depends on specific error.BEA-(retired) Error: Failed cmd operation: msgDescription A deployment operation failed.Cause Error encountered during
31、 deployment.Action Depends on specific error.BEA-(retired) Info: cmd operation completed successfully.Description A deployment operation was successfulBEA-(retired) Info: Connection released during running cmd operation.Description The deployment operation will continue but no further status will be
32、 reported.Cause The deployment tool released the its deployment manager.Action None required.BEA-(retired) Error: Unable to read arc: msgDescription Unable to enumerate archive entries due to IOExceptionCause IO FailuresAction NoneBEA- Info: Restored configuration for module, modDescription The in-m
33、emory configuration for a module was updated on request.Cause DeploymentConfiguration.restoreDConfigBean was invokedBEA- Info: Removed configuration for module, modDescription The in-memory configuration for a module was deleted on request.Cause DeploymentConfiguration.removeDConfigBean was invokedB
34、EA- Info: Saved configuration for module, modDescription The in-memory configuration for a module was written to diskCause DeploymentConfiguration.saveDConfigBean was invokedBEA- Info: Restored configuration for application, appDescription The in-memory configuration for an application was updated o
35、n request.Cause DeploymentConfiguration.restore was invokedBEA- Info: Saved configuration for application, appDescription The in-memory configuration for an application was written to diskCause DeploymentConfiguration.save was invokedBEA- Error: Unable to introspect on bean, clazzDescription An Intr
36、opsection exception occurred while determining a beans key value.Cause Internal errorAction None requiredBEA-(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 configur
37、ation 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 var
38、iable declarations.BEA-(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
39、 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-(retired) Warning: The configuration for module name is defined using an unsupported, DTD-based, descriptor.Description The descriptor
40、 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-(retired) Warning: An exception occurred while parsing descriptor for module name at uri: msg.Description IO failures were
41、 detected or the descriptor is invalid.Cause Check error message for specific problem.Action None required.BEA- 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 probl
42、em.Action None required.BEA-(retired) Error: Unable to explode embedded archive, fileDescription The application contains embedded archives which need to be exploded to access all descriptors.Cause Sharing violation.Action None required.BEA- Error: Unable to define application install directory at f
43、ile. 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 directoryBEA- Error: The descriptor at file could not be parsed.Description The desc
44、riptor contains syntax errorsCause The descriptor is invalidAction NoneBEA- 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.Caus
45、e Missing descriptor fileAction Place the necessary descriptor in the archive or its external configuration areaBEA- Warning: No plan document at fileDescription 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