The J2EE Deployment SPI1.0 catalog contains messages in the range BEA260000 - BEA260999. Messages in this catalog are part of the weblogic.deploy.api.internal Internationalization package and the weblogic.deploy.api.internal Localization package.
|
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 targetting information provided for op operation.
|
Description
|
The operation requires something to deploy and targetting 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 |
<tr
分享到：
Global site tag (gtag.js) - Google Analytics
|
相关推荐
很详尽的weblogic错误，运行weblogic会遇到一些错误，这个文档将详细介绍这些错误及解决的方法。
weblogic12c部署webservice错误问题WSSERVLET11: 无法解析运行时描述符: java.lang.IllegalStateException: MASM0001:
Weblogic反序列化远程代码执行漏洞(CVE-2018-2893)以及安装步骤
NULL 博文链接：https://qinchaoyong.iteye.com/blog/805452
JavaEE5实用教程——基于WebLogic和Eclipse程序源代码
weblogic部署，常见错误解决(收集)
NULL 博文链接：https://442136713.iteye.com/blog/378815
weblogic weblogic weblogic weblogic
可以在weblogic下开发的websocket完整示例，希望对你有用，谢谢！
weblogic下开发web项目时修改java文件不用重启的绿色方法，不用修改weblogic的配置文件、不用jar
liferay5.1布署到weblogic9.2 自己弄个给不会的瞧瞧
cobertura和weblogic整合使用-代码覆盖率测试 里面详细步骤和使用说明，并附加xml文件，不懂的可以QQ我，147806015，
NULL 博文链接：https://ligaosong.iteye.com/blog/1750085
基于weblogic的jsp预编译，通过windows批处理方式对jsp预编译
weblogic监控 weblogic调优 weblogic版本区别 weblogic启动关闭脚本
使用该示例代码可以自动转换weblogic的配置文件格式为jboss支持的格式,是从weblogic到jboss进行项目移植必不可少的一环. 解决了手工修改的工作量和容易出现错误的问题.
安装weblogic 怎样部署 怎样配置多数据库weblogic10.3错误补丁
20180717官网发布Weblogic反序列化远程代码执行漏洞(CVE-2018-2893)漏洞修复补丁
weblogic生产模式下更新步骤
当IdleThreads的值为0时，QueueLength会出现数值。如果QueueLength维持在较高位置，且不下降时，有死机危险。但只要值在变，就说明系统还在运行. WebLogic服务的监控 •MemoryUsage内存的使用情况 主要看垃圾回收...