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错误通常以`WLS-`或`BEA-`开头，每个错误代码都对应一个具体的错误条件。例如，`WLS-00001`表示服务器启动失败，`BEA-000365`是关于安全认证的问题。查阅官方文档或在线资源可以帮助我们理解这些错误代码的...
错误信息"无法解析运行时描述符: java.lang.IllegalStateException: MASM0001:"指出在部署Web服务时遇到了异常情况。这个错误代码MASM0001通常与WebLogic的模块组装（Module Assembly）过程有关，该过程是将应用组件...
本篇文章将针对“在WebLogic部署出现的错误”这一主题，详细探讨可能遇到的问题及解决方案。 首先，WebLogic是Oracle公司开发的一款企业级Java EE应用服务器，用于运行和管理Java应用程序。在部署过程中，错误通常...
1. **漏洞原理**：WebLogic Server在处理某些类型的数据流时，没有正确地验证输入，这使得攻击者可以构造特殊的Java序列化对象并将其发送到服务器，从而触发远程代码执行。攻击者一旦成功利用此漏洞，可以在目标...
在使用 Weblogic 服务器时，经常会遇到一些常见的问题和错误，本文总结了其中的一些解决方法，旨在帮助开发者快速排除错误，提高开发效率。 1. Unmarshaller failed 问题的解决方法 在使用 Weblogic 9.2 版本时，...
1. **创建或选择域**：WebLogic Server的管理是基于域的，每个域包含一组服务器和相关的配置信息。你可以通过`wlst`（WebLogic Scripting Tool）或者管理控制台来创建新域。 2. **打包应用**：将你的Java EE应用...
在WebLogic服务器环境中，开发和调试Java Web应用程序时，频繁的服务器重启会极大地降低开发效率。标题和描述中提到的“绿色方法”是指一种优化的、无需修改WebLogic配置文件或使用额外JAR的方式，来实现在WebLogic...
这些文档是部署和升级WebLogic Server时的重要参考，可以确保系统的稳定性和兼容性。 总的来说，Oracle WebLogic Server的版本更新伴随着对新技术的支持和对旧技术的兼容，确保了用户能够在不断变化的技术环境中...
本示例代码是针对在WebLogic上开发WebSocket应用的一个详细实例，旨在帮助开发者理解和实践WebSocket在WebLogic中的应用。 WebSocket API是基于HTTP的，但与HTTP不同的是，它在建立连接后可以保持长时间开放，从而...
综上所述，"JavaEE5实用教程——基于WebLogic和Eclipse程序源代码"涵盖了从基础组件到高级特性的广泛内容，旨在帮助开发者利用JavaEE5的简化特性，结合WebLogic Server的稳定性和Eclipse的高效开发工具，创建高质量...
JDK 内存是 Weblogic 服务器的核心组件之一，负责 Java 应用程序的运行时环境。合理的 JDK 内存设置可以确保服务器的稳定运行，防止服务器出现内存溢出和卡顿等问题。在 Weblogic 10.3 中，可以通过修改 `weblogic\...
由于Weblogic服务器在处理这些请求时未能充分检查输入，恶意代码得以执行。一旦攻击成功，攻击者可以执行任意系统命令，获取敏感信息，部署恶意软件，或者进行其他恶意操作。 Oracle在2018年7月17日发布了该漏洞的...
在部署配置中，确保WebLogic知道已经预编译过的JSP文件，这样服务器在启动时就会直接加载预编译的Servlet，而不会尝试重新编译JSP。 五、优化与注意事项 - 预编译可能会增加磁盘空间的占用，因为每个JSP都会生成一...
1. **备份现有环境**：在进行任何更新操作之前，首先需要对当前的WebLogic环境进行全面备份，包括但不限于应用程序代码、配置文件、数据源定义等。这一步骤至关重要，一旦更新过程中出现问题，可以迅速恢复到更新前...
这类问题通常表现为访问Web应用时出现500错误，即“内部服务器错误”（Internal Server Error）。根据RFC 2068《Hypertext Transfer Protocol -- HTTP/1.1》规范，500错误表示服务器遇到了一种它无法处理的情况，...
cobertura和weblogic整合使用-代码覆盖率测试 里面详细步骤和使用说明，并附加xml文件，不懂的可以QQ我，147806015，
这里提到的"weblogic到jboss转换的示例代码"就是一个这样的例子，它提供了一个自动化工具，帮助用户将WebLogic服务器的配置文件转换为JBoss服务器兼容的格式，极大地简化了迁移过程，避免了手动修改带来的工作量和...
在`user_projects/domains`目录下找到对应的域文件夹，双击`startWebLogic.cmd`启动服务。 3. **访问WebLogic控制台** 通过浏览器访问`http://localhost:9999/console`，使用建域时设定的用户名和密码登录控制台，...
在WebLogic Server 9.2至10.0版本中，用户可能会遇到一个特定的错误，即“java.lang.AssertionError: Registered more than one instance with the same objectName”。这个错误主要表现为服务器启动后，在Admin ...
这个漏洞允许远程攻击者未经身份验证就执行任意代码，只需通过WebLogic服务器的T3协议发送特制的请求。由于这个漏洞的存在，攻击者可以完全控制受影响的系统，执行任意操作，如数据窃取、恶意软件传播或系统破坏。...