The J2EE 1.0
catalog contains messages in the range
160000 - 169899.
Messages in this catalog are part of the
weblogic.j2ee
Internationalization package and the
weblogic.i18n
Localization package.
|
160000 (retired)
|
Error: Error Application Instance not found : appName
|
|
160001
|
Error: Error deploying name: msg
|
Description
| Applications can be deployed via the admin console or weblogic.deploy tool. |
|
Cause
| The application is misconfigured. See logged exception for more details. |
|
Action
| Check your config.xml to ensure that the component MBean is wrapped in a valid application mbean. And has a valid URI and Target attribute. |
|
|
160002 (retired)
|
Error: Error deploying EJB Component : msg
|
|
160003
|
Info: Deployed : appName
|
|
160004
|
Info: Undeployed : appName
|
|
160005 (retired)
|
Error: Error undeploying application appName: msg
|
|
160006 (retired)
|
Error: Error undeploying EJB Component : msg
|
|
160007 (retired)
|
Warning: You are running WebLogic Server with J2EE 1.3 features enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1 is of a non-final version of the appropriate specification. It is subject to change in future releases once the specification becomes finalized. This may cause application code developed for BEA WebLogic Server 6.1 that uses the new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in future releases of BEA WebLogic Server.
|
|
160008
|
Warning: component componentName, could not instantiate lifecycle handler class classname. Must contain public default constructor! (e).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160009
|
Warning: component componentName, lifecycle handler class classname not found in component archive (e).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160010
|
Warning: component componentName, lifecycle handler class classname not found in component archive (e).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160011
|
Warning: component componentName, could not find classloader during load of lifecycle handler class classname (e).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160012
|
Warning: component componentName, unexpected problem during load of lifecycle handler class classname (t).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160013
|
Warning: component componentName, missing propname in property file filename.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160014
|
Warning: component componentName, unexpected problem during load attempt of property file filename.
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160015
|
Warning: component componentName, exception in lifecycle handler classname.msgName (t).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160016
|
Warning: component componentName, lifecycle handler class classname must implement weblogic.j2ee.lifecycle.LifecycleHandler or extend weblogic.j2ee.lifecycle.LifecycleAdapter (e).
|
Description
| This message is no longer used. |
|
Cause
| This message is no longer used. |
|
Action
| This message is no longer used. |
|
|
160017 (retired)
|
Error: Unable to find Application Container for application named - annotation while loading class className.\nException is:\ne
|
|
160018
|
Warning: ComponentMBean: Name = Name, Type = Type - Targeted on this server but, no corresponding module found in application descriptor. The component mbean is being Ignored.
|
Description
| The mbean configuration (config.xml) lists the modules in an application and where they are targeted. This list should match the list of modules in the deployment descriptor of the application. If there is a mismatch the information in the application.xml overrides. For example, in this case if the module does not exist in the application.xml it will not be deployed. |
|
Cause
| This could happen because the module entry is missing in application.xml. Or a bad component mbean is configured in the config.xml |
|
Action
| Reconcile the deployment file with its configuration in config.xml. |
|
|
160019 (retired)
|
Error: ComponentMBean: objectName - Targeted on this server. Unable to create a weblogic.application.Module for it. Ignored.
|
Description
| This should never happen. Indicates that there is no module container in WLS which recognizes this component MBean. |
|
|
160020 (retired)
|
Error: Failed to parse deployment descriptor for path. Error: th
|
|
160021 (retired)
|
Error: Failed to remove component mbean (comp) from application mbean (app). Error - th
|
Description
| This component was not found in the application descriptors. The target server may attempt to deploy this module and fail. |
|
|
160022 (retired)
|
Error: Invalid exception thrown by module msg.
|
|
160023 (retired)
|
Error: Application container already exists for application mbean with name: name
|
|
160024 (retired)
|
Error: Application container not found for application mbean with name: name
|
|
160025
|
Error: No file corresponding to path attribute path of application app
|
Description
| This deployment path is provided in the deployment request. This is initiated from the admin console or weblogic.Deployer tool. |
|
Cause
| Deployment path provided does not exist. |
|
Action
| Correct the path provided in the request to point to the right place or move the deployment to the path provided. |
|
|
160026 (retired)
|
Error: You must be on the admin server to perform the following action: action
|
|
160027 (retired)
|
Error: Deployment name is null.
|
|
160028
|
Error: No J2EE deployment descriptor found at "path".
|
Description
| The directory specified for deployment must contain a standard J2EE deployment descriptor. For example - META-INF/application.xml for EARs , WEB-INF/web.xml for web applications. See documentation for details on how to package applications. |
|
Cause
| Some deployment descriptor is missing. See message body. |
|
Action
| Ensure that the deployment provided has the required deployment descriptors. |
|
|
160029
|
Error: I/O error while reading deployment - msg.
|
Description
| WLS is trying to validate the deployment by checking for all valid descriptors. |
|
Cause
| See logged exception. |
|
Action
| This could happen because of some file system problem like insufficient permissions on the file. See message in exception logged. |
|
|
160030 (retired)
|
Error: Unable to setPath on ApplicationMBean for path: msg
|
|
160031
|
Error: Error creating VirtualJar path: msg
|
Description
| WLS cannot find the deployment at the path specified. |
|
Cause
| Please see exception logged. |
|
Action
| Double check the deployment path provided in the deployment request. |
|
|
160032
|
Error: Unable to create mbean Name: name Type: type String msg Exception: t
|
Description
| MBean creation Error. Deployment request cannot proceed. |
|
Cause
| See message body. |
|
Action
| See exception message logged. |
|
|
160033 (retired)
|
Error: MBean Error adding component comp to application app: msg
|
|
160034
|
Error: Module uri not Found in path path.
|
Description
| Application deployment descriptor - application.xml contains the list of defined modules for the application and their locations within the application. |
|
Cause
| Referred module is defined in application.xml, however does not exist in the deployment provided. |
|
Action
| Add the module to your deployment, or remove the module entry from the application.xml, as appropriate. |
|
|
160035
|
Error: Error retrieving files from admin server for component moduleName of application appName: t.
|
Description
| The server could not create the temp files needed to deploy this application. Possible reasons for this are that the disk is full, the .wlnotdelete directories have been deleted, or for some reason, the WebLogic process does not have permission to write to the filesystem. |
|
Cause
| Caused when the temp file could not be created or written to. |
|
Action
| Make sure the disk isn't full. |
|
|
160036 (retired)
|
Error: Error updating files from admin server for component moduleName of application appName: t.
|
|
160037
|
Info: J2EE service initializing.
|
|
160038
|
Error: Failed to deploy a Mail Session.
|
Description
| Mail sessions are declared using resource references in the module deployment descriptor. |
|
Cause
| Some of the reasons for failure could be failure to create a mail session or bind it to JNDI. See exception for more details. |
|
Action
| Check the error reported in the exception. |
|
|
160039
|
Error: Failed to undeploy a Mail Session.
|
Description
| Mail sessions are declared using resource references in the module deployment descriptor. They are undeployed along with the deployment. |
|
Cause
| JNDI unbind error. |
|
Action
| Check the error reported in the exception. |
|
|
160040
|
Info: Deployed MailSession named jndiName
|
|
160041
|
Info: Undeployed MailSession named jndiName.
|
|
160042
|
Info: Adding new module "moduleName" To application named "appName".
|
Description
| A module was found in application.xml which has no corresponding ComponentMBean. WLS will create a componentMBean for it and add it to the application. |
|
Cause
| New module found in application.xml |
|
Action
| No action required. |
|
|
160043
|
Error: Missing deployment descriptor "dd" at "path"
|
Description
| The directory specified for deployment must contain a standard J2EE deployment descriptor. For example - META-INF/application.xml for EARs , WEB-INF/web.xml for web applications. See documentation for details on how to package applications. |
|
Cause
| Some deployment descriptor is missing. See message body. |
|
Action
| Create a valid deployment descriptor and it to the deployment as pointed out in the message. |
|
|
160044
|
Error: The deployment file "path" has an unrecognized extension.
|
Description
| For archived deployments, only standard extensions defined by J2EE are supported. For example .jar for EJBs, .rar for connector modules, .war for web modules and .ear for enterprise applications. |
|
Cause
| The path provided for deployment points to a file, and the file does not have a valid extension. |
|
Action
| Make sure that the deployment is a valid jar file with a J2EE standard extension. |
|
|
160045
|
Error: The module moduleName in application appName cannot be individually redeployed because it shares a classloader with other modules.
|
Description
| The module moduleName in application appName shares a classloader with other modules in application appName. For this reason, you cannot redeploy this module by itself. You must redeploy the whole application. |
|
Cause
| When a module or part of a module is redeployed, it may need to reload its classloader in order to be able to load classes that have changed. In this case, all modules that share that classloader or a classloader that is an offspring of that classloader will need to be redeployed too. |
|
Action
| Do not attempt to redeploy this module individually. Redeploy the entire application, instead. |
|
|
160046
|
Error: Cannot use a JMS connection factory because the object is of the wrong type
|
Description
| A JMS connection factory that was retrieved from JNDI is either a QueueConnectionFactory when a TopicConnectionFactory was expected, or vice versa, or the object is of neither type. |
|
Cause
| Either the name of the connection factory in the deployment descriptor XML files is wrong, or the wrong object was bound into JNDI. |
|
Action
| Check the name in the XML files against what is actually registered in JNDI. |
|
|
160047
|
Error: A JMS session pool could not be created because the propName property was not specified
|
Description
| A JMS session pool was either created directly by the user or by internal container code, and it did not properly specify a property. |
|
Cause
| If the JMSSessionPool class is not being used directly by the user, then this is an internal error. |
|
Action
| Contact BEA support. |
|
|
160048
|
Error: JNDI lookup of the JMS connection factory name failed
|
Description
| The server attempted to look up a JMS connection factory at the specified location, but the lookup failed. |
|
Cause
| The remote JNDI server or JMS server is not available, or the name was incorrectly specified. |
|
Action
| Check that the server is running, and check the name in the deployment descriptor XML files. |
|
|
160049
|
Error: An error occurred while registering the JMS connection with JTA
|
Description
| An error occurred while attempting to register a JMS session resource with the transaction system. |
|
Cause
| The JMS connection factory specified does not properly support XA, or something is wrong with the transaction system. |
|
Action
| Check the linked exception, and verify that the JMS provider properly supports XA. |
|
|
160050
|
Error: The JMS session pool is shutting down
|
Description
| An operation was attempted against a JMS session pool, but the pool is in the middle of shutting down. |
|
Cause
| The pool is being shut down, possibly because of an error. |
|
Action
| Check for other errors that indicate why the pool is being shut down, and retry the operation. |
|
|
160051
|
Error: Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container
|
Description
| An EJB or servlet was deployed using a JMS connection factory resource that has a res-auth setting of Container, but the application code attempted to open a JMS connection using a username and password. In this case, the username and password are supplied by WebLogic Server. |
|
Cause
| The application code is not using the J2EE APIs properly. |
|
Action
| Either remove the username and password, or set the res-auth element to Application. |
|
|
160052
|
Error: A PooledConnectionFactory object with an invalid external version of version was found
|
Description
| A PooledConnectionFactory could not be read from JNDI because the version of WebLogic Server that stored it is not compatible with the version that is retrieving it. |
|
Cause
| The version of WebLogic Server that stored it is not compatible with the version that is retrieving it. |
|
Action
| Contact BEA support. |
|
|
160053
|
Error: The JMS method methodName may not be called inside an EJB or servlet
|
Description
| The application code attempted to call a method on the JMS API that is not allowed by the J2EE specifications. Certain methods are restricted for use by the application server so that it can maintain a pool of JMS objects. |
|
Cause
| The application code has violated the J2EE specifications. |
|
Action
| Change the code to avoid calling the specified method. |
|
|
160054
|
Error: The pooled JMS session is enlisted in another transaction and may not be used elsewhere
|
Description
| A pooled JMS session is enlisted in a transaction, and it either may not be used in another transaction, or it may not be used outside a transaction. |
|
Cause
| Check the application code to ensure that a pooled JMS session (retrieved from the JNDI java:comp/env/jms context) is not kept between transactions. It should be closed so that it is returned to the pool. |
|
Action
| Check the application code. |
|
|
160055
|
Error: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available
|
Description
| An EJB or servlet attempted to use a wrapped JMS session that it acquired from a resource-ref inside a transaction context, but the JMS session cannot participate in the transaction because two-phase commit is not available from the connection factory. |
|
Cause
| The JMS connection factory specified does not support two-phase commit. |
|
Action
| For WebLogic JMS, two-phase commit may be enabled by setting the "UserTransactionsEnabled" flag on the JMS connection factory. For other JMS providers, you must specify a JMS connection factory that supports XA. |
|
|
160056
|
Error: Error creating or instantiating a wrapper for class name
|
Description
| The server was not able to create a wrapper for the specified class. The wrapper is used to intercept certain methods from the JMS provider to provide WebLogic Server-specific behavior. |
|
Cause
| There may be an error with the classpath, or with the underlying JMS provider's code. |
|
Action
| Check the classpath. If this does not fix the problem, contact BEA support. |
|
|
160057
|
Error: A pooled JMS connection is being closed because an error was detected on the connection: msg
|
Description
| There was a problem with a JMS connection that was being used in a servlet or EJB. The connection has been closed, and will be re-opened the next time it is used if possible. |
|
Cause
| The JMS server is unavailable, or there is some other problem with it that makes it impossible to send or receive messages. |
|
Action
| Check the configuration parameters for the JMS server, and check that it is available on the network. |
|
|
160058
|
Debug:
|
Description
| Uncataloged debug message. |
|
|
160059
|
Error: The JMS object may not be used because it has been closed
|
Description
| The "close" method has been closed on a JMS object, so it is no longer possible to invoke methods on the object. |
|
Cause
| The object has been closed. |
|
Action
| This is a programming error and should be fixed on the users's part. |
|
|
160060
|
Error: An error occurred while committing or rolling back a JTA transaction used for a JMS operation by the J2EE container
|
Description
| The transaction system was unable to commit or rollback a transaction that the J2EE container started in order to handle a JMS operation. |
|
Cause
| There was a problem with the transaction system. |
|
Action
| See the linked exception for more information. |
|
|
160061
|
Error: The JMS session pool has been disabled
|
Description
| The resource pool subsystem has disabled the JMS session pool, so it may not be used. |
|
Cause
| An administrative action was taken. |
|
Action
| Re-enable the session pool. |
|
|
160062
|
Error: There was an error with a resource pool used to pool JMS sessions
|
Description
| The resource pool subsystem detected an error which makes the JMS session pool unusable. |
|
Cause
| There is a problem with the resource pool. |
|
Action
| See the linked exception for details. |
|
|
160063
|
Warning: There was an error while closing a JMS session pool or a pooled JMS connection: errorMsg The pool or object was forcibly closed.
|
Description
| The session pool or pooled connection object encountered an error while closing, but it was closed anyway. |
|
Cause
| See the linked exception for more information. |
|
Action
| No action required. |
|
|
160064
|
Warning: There was an error while making the initial connection to the JMS session pool named poolName. The server will attempt the connection again later. The error was errorMsg
|
Description
| When an EJB, JSP, or servlet that uses a JMS connection factory as a resource-reference is first deployed, the server tries to connect to the JMS provider so it can perform XA recovery. The server will attempt the connection later when the resource reference is actually used. |
|
Cause
| See the error message from the JMS provider. |
|
Action
| No action necessary. |
|
|
160065
|
Error: A JMS message consumer could not be created using a temporary queue or topic that was created using another connection
|
Description
| TemporaryQueue and TemporaryTopic objects, once created, may only be used to create message consumers when the consumers were created using the same connection that was used to create the temporary destination. |
|
Cause
| Application programming error. |
|
Action
| Change application code. |
|
|
160066
|
Error: The classloader-structure definition for the application named appName has been removed. When you remove the classloader-structure definition from weblogic-application.xml, you must reload entire application.
|
Description
| The classloader-structure definition defines the organization of the classloaders in an application. This is an optional definition, however, if you have such a definition, you may not remove it without reloading the application. |
|
Cause
| The classloader-structure definition was removed from weblogic-application.xml. |
|
Action
| Redeploy entire application. |
|
|
160067
|
Error: The classloader-structure definition for the application named appName has changed in an incompatible way. The module with uri uri has been moved to a different node.
|
Description
| When modifying the classloader-structure of an application, only certain changes are allowable during an incremental update. For this type of change you must redeploy the full application. |
|
Cause
| A module was moved from one classloader node to a different classloader node. |
|
Action
| Redeploy application. |
|
|
160068
|
Error: The classloader-structure definition for the application named appName has changed in an incompatible way. The node node was removed without removing module uri.
|
Description
| When modifying the classloader-structure of an application, only certain changes are allowable during an incremental update. For this type of change you must redeploy the full application. |
|
Cause
| A module was moved from one classloader node to a different classloader node. |
|
Action
| Redeploy application. |
|
|
160069
|
Error: Error while looking for web services files: err
|
Description
| The system was trying to determine if a web application is also a web service. An IOException was thrown while trying to read the descriptors. |
|
Cause
| An IOException occured while accessing web services files |
|
Action
| See stack trace for details |
|
|
160070
|
Error: Application app received exception processing module module: err.
|
Description
| An exception occurred during the deployment of a module. |
|
Cause
| This is due to a deployment failure at the module level. |
|
Action
| See exception message for details. |
|
|
160071
|
Error: Listener Class className URI: classURI is not a valid file
|
Description
| Need to double check descriptor listener definition for correctness |
|
Cause
| Received IOException when trying to get canonical path for class URI |
|
Action
| log warning but continue deployment |
|
|
160072
|
Error: Listener Class className file: pathName does not exist
|
Description
| Need to double check descriptor listener definition for correctness |
|
Cause
| Cannot locate the file on the file system. |
|
Action
| log warning but continue deployment |
|
|
160073
|
Error: ClassNotFoundException during registration of Listener className, message
|
Description
| Need to double check descriptor listener definition for correctness |
|
Cause
| ClassNotFoundException during class instantiation |
|
Action
| log warning but continue deployment |
|
|
160074
|
Error: InstantiationException during registration of Listener className, message
|
Description
| Need to double check descriptor listener definition for correctness |
|
Cause
| InstantiationException during class instantiation |
|
Action
| log warning but continue deployment |
|
|
160075
|
Error: IllegalAccessException during registration of Listener className, message
|
Description
| Need to double check descriptor listener definition for correctness |
|
Cause
| IllegalAccessException during class instantiation |
|
Action
| log warning but continue deployment |
|
|
160076
|
Error: You must include all of affected in your files list to modify components
|
Description
| You attempted to reload a module or set of modules which have classloader interdependencies with other modules not declared in the reload. In order to reload these modules, you must reload all the modules in the set listed in the exception. |
|
Cause
| A module reload requires the classloader associated with that module to be reloaded. If other modules share that classloader or have a classloader which is a child of that classloader, then they must be reloaded, too. |
|
Action
| Include full set of interdependent modules in the target list for the reload. |
|
|
160077
|
Error: Could not find ClassLoader associated with module
|
Description
| The system was checking the ClassLoader consistency during a reload. The ClassLoader for one of the modules declared in the reload was not found. |
|
Cause
| This can happen if you are modifying the structure of the ClassLoader hierarchy during a reload. |
|
Action
| Reload the whole app rather than doing a partial redeploy. |
|
|
160078
|
Error: There are no modules to deploy on server for application app. Check if the target is set correctly and the module physically exists in the deployment.
|
Description
| The deployment failed because a module does not exist on the target is was deployed to. |
|
Cause
| An attempt was made to deploy a module on a node where the module is unavailable |
|
Action
| Verify that the targetting information is correct and there is a module that exists for each target listed. |
|
|
160079
|
Error: There is no module defined with the uri uri which is used in the classloader-structure declaration in weblogic-application.xml for app.
|
Description
| The classloader-declaration in META-INF/weblogic-application.xml specifies uri which does not correspond to any uri in the module list of META-INF/application.xml |
|
Cause
| This is an application configuration error. |
|
Action
| Make the classloader-structure definition in weblogic-application.xml be consistent with the module set in application.xml. |
|
|
160080
|
Error:
|
Description
| The classloader-declaration in META-INF/weblogic-application.xml specifies the same uri twice for two different nodes. |
|
Cause
| This is an application configuration error. |
|
Action
| Remove the duplicate uri declaration from the classloader-structure in weblogic-application.xml. |
|
