J2EE Subsystem Messages

The J2EE1.0 catalog contains messages in the range
BEA-160000 - BEA-169899. Messages in this catalog are part of the
weblogic.j2ee
Internationalization package and the weblogic.j2ee Localization package.

BEA-160000(retired)

Error: Error Application Instance not found : appName

BEA-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. Check your server log for errors.

BEA-160002(retired)

Error: Error deploying EJB Component : msg

BEA-160003(retired)

Info: Deployed : appName

BEA-160004(retired)

Info: Undeployed : appName

BEA-160005(retired)

Error: Error undeploying application appName: msg

BEA-160006(retired)

Error: Error undeploying EJB Component : msg

BEA-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.

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.

BEA-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.

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.

BEA-160026(retired)

Error: You must be on the admin server to perform the following action: action

BEA-160027(retired)

Error: Deployment name is null.

BEA-160028(retired)

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.

BEA-160029(retired)

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.

BEA-160030(retired)

Error: Unable to setPath on ApplicationMBean for path: msg

BEA-160031(retired)

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.

BEA-160032

Error: Unable to create mbean Name: name Type: type Exception: msg

Description

MBean creation Error. Deployment request cannot proceed.

Cause

See message body.

Action

See exception message logged.

BEA-160033(retired)

Error: MBean Error adding component comp to application app: msg

BEA-160034(retired)

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.

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. If the .wlnotdelete directory has been deleted or write protected, the server will not be able to write temporary files. Ensure that this directory exists and the server is able to write to it.

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.

BEA-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.

BEA-160040

Info: Deployed MailSession named jndiName

Description

retired?

BEA-160041

Info: Undeployed MailSession named jndiName.

Description

retired?

BEA-160042(retired)

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.

BEA-160043(retired)

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. Note that the META-INF and WEB-INF directory must be capitalized

BEA-160044(retired)

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.

BEA-160045(retired)

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.

BEA-160046(retired)

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.

BEA-160047(retired)

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 Oracle Customer Support.

BEA-160048(retired)

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.

BEA-160049(retired)

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.

BEA-160050(retired)

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.

BEA-160051(retired)

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.

BEA-160052(retired)

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 Oracle Customer Support.

BEA-160053(retired)

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.

BEA-160054(retired)

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.

BEA-160055(retired)

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.

BEA-160056(retired)

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 providers code.

Action

Check the classpath. If this does not fix the problem, contact Oracle Customer Support.

BEA-160057(retired)

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.

BEA-160058

Debug: msg

Description

Uncatalogued debug message.

BEA-160059(retired)

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.

BEA-160060(retired)

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.

BEA-160061(retired)

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.

BEA-160062(retired)

Error: There was an error with a resource pool used to pool JMS sessions

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.

BEA-160064(retired)

Warning: There was an error while making the initial connection to the JMS resource named poolName from within an EJB or a servlet. 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. The server will attempt the connection again later when the JMS resource is actually used.

Cause

See the error message from the JMS provider.

Action

No action necessary.

BEA-160065(retired)

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.

BEA-160066(retired)

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.

BEA-160067(retired)

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.

BEA-160068(retired)

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.

BEA-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.

The server was attempting to instantiate a listener class and received an IllegalAccessException

Cause

The server does not have access to a field or method it requires to instantiate the class

Action

Ensure the listener class has necessary access to fields and methods.

BEA-160076(retired)

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

Either include the full set of interdependent modules in the target list for the reload or redeploy the whole application.

BEA-160077(retired)

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.

BEA-160078(retired)

Error: None of the modules of application 'app' in 'META-INF/application.xml' are configured in the 'Application' entry in 'config.xml' to be targeted to 'server'.

Description

The list of modules in the application descriptor is the master list of modules used for deployment. At least one module in the application descriptor should have a corresponding entry in the 'Application' entry in the 'config.xml'.

Cause

The URI of any module in 'application.xml' does not match any URIs in the 'Application' entry in 'config.xml'. This can happen if the entry was modified or created manually.

Action

Verify that at least one module from 'application.xml' is listed in the 'Application' entry in the config.xml. And further that their URIs match.

BEA-160079(retired)

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.

BEA-160080(retired)

Error: uri is declared twice in classloader-structure declaration in weblogic-application.xml of app.

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.

BEA-160081(retired)

Warning: The JMS connection factory resource resName declared in the EJB "ejbName" as part of application "appName" does not support XA. It cannot be used inside a transaction context.

Description

The a JMS connection factory was defined as a resource-reference for the specified EJB. Since the connection factory does not support XA, it may not be used inside a transaction context, or an exception will be thrown.

Cause

If the specified JMS connection factory is intended to be used inside a transaction context, then the EJB was configured improperly.

Action

If the specified JMS connection factory is intended for use inside a transaction context, then the connection factory used by the EJB must be changed so that it supports XA, or the EJB descriptor must be changed to point to a different connection factory. However, if the connection factory will never be used inside a transaction context, then no action is necessary.

BEA-160082(retired)

Warning: There was an error while making the initial connection to the JMS resource named poolName from the EJB "ejbName" inside application "appName". The server will attempt the connection again later. The error was errorMsg

Description

When an EJB, that uses a JMS connection factory as a resource-reference is first deployed, the server tries to connect to the JMS provider. The server will attempt the connection again later when the JMS resource is actually used.

Cause

See the error message from the JMS provider.

Action

No action necessary.

BEA-160083

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' could not be resolved. The ejb-jar file 'invalidURI' could not be found in this ear file.

Description

This qualified ejb-link has an invalid qualification. The path to the module containing the target EJB is incorrect.

Cause

The path to the target EJB does not exist in the application.

Action

The ejb-link must be fixed to point to the module containing the target EJB.

BEA-160084

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the module 'moduleURI' could not be resolved. The ejb-jar file 'invalidURI' could not be found in this ear file.

Description

This qualified ejb-link has an invalid qualification. The path to the module containing the target EJB is incorrect.

Cause

The path to the target EJB does not exist in the application.

Action

The ejb-link must be fixed to point to the module containing the target EJB.

BEA-160085

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' could not be resolved. The ear module 'invalidURI' does not contain an EJB with the name 'unqualifiedLink'.

Description

This qualified ejb-link could not be resolved. Although the link qualification could be resolved, the specified EJB could not be found in the module.

Cause

The specified EJB doesn"t exist in the module.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160086

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the module 'moduleURI' could not be resolved. The ear module 'invalidURI' does not contain an EJB with the name 'unqualifiedLink'.

Description

This qualified ejb-link could not be resolved. Although the link qualification could be resolved, the specified EJB could not be found in the module.

Cause

The specified EJB doesn"t exist in the module.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160087

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' did not resolve to a bean with component interfaces. Please ensure the link is correct.

Description

Although the ejb-link did resolve to an EJB, it did not resolve to an EJB with component interfaces. For example, the link may have resolved to a message-driven bean.

Cause

The link did not resolve to a valid EJB.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160088

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the module 'moduleURI' did not resolve to a bean with component interfaces. Please ensure the link is correct.

Description

Although the ejb-link did resolve to an EJB, it did not resolve to an EJB with component interfaces. For example, the link may have resolved to a message-driven bean.

Cause

The link did not resolve to a valid EJB.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160089

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' could not be resolved. No EJB named 'link' with component interfaces exists in the application. Please ensure the link is correct.

Description

This unqualified ejb-link could not be resolved. No EJB in the application was found to have a name equal to the ejb-link value.

Cause

The specified EJB doesn"t exist in the module.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160090

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the module 'moduleURI' could not be resolved. No EJB named 'link' with component interfaces exists in the application. Please ensure the link is correct.

Description

This unqualified ejb-link could not be resolved. No EJB in the application was found to have a name equal to the ejb-link value.

Cause

The specified EJB doesn" exist in the module.

Action

The ejb-link must be fixed to point to a valid EJB.

BEA-160091

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' is ambiguous. The following list of application modules contain an EJB with the name 'link': list. Please qualify this ejb-link to remove the ambiguity.

Description

This unqualified ejb-link resolved to multiple EJBs in the application. Each of the modules listed contains an EJB that the ejb-link resolves to.

Cause

The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action

The ejb-link must be fixed to point to a single EJB.

BEA-160092

Error: Error: The ejb-link 'link' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the module 'moduleURI' is ambiguous. The following list of application modules contain an EJB with the name 'link': list. Please qualify this ejb-link to remove the ambiguity.

Description

This unqualified ejb-link resolved to multiple EJBs in the application. Each of the modules listed contains an EJB that the ejb-link resolves to.

Cause

The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action

The ejb-link must be fixed to point to a single EJB.

BEA-160093

Error: Error: The ejb-link 'link' declared in the ejbRefType 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' could not be established. The target of the ejb-link does not have interfaceType interfaces. Please ensure the link is correct.

Description

The ejb-link in this ejb-ref or ejb-local-ref resolves to a bean that does not have interfaces compatible with the ref type. For example, an ejb-ref must resolve to an EJB that exposes remote interfaces. Similarly, an ejb-local-ref must resolve to an EJB that exposes local interfaces.

Cause

The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action

Ensure that the target of the ejb-link is indeed the EJB you would like to refer to. If this is true, you can either add component interfaces to this EJB that are compatible with the ref type or you can change the ref type to be compatible with the interfaces exposed by the target EJB.

BEA-160094

Error: Error: The ejb-link 'link' declared in the ejbRefType 'ejbRefName' in the module 'moduleURI' could not be established. The target of the ejb-link does not have interfaceType interfaces. Please ensure the link is correct.

Description

The ejb-link in this ejb-ref or ejb-local-ref resolves to a bean that does not have interfaces compatible with the ref type. For example, an ejb-ref must resolve to an EJB that exposes remote interfaces. Similarly, an ejb-local-ref must resolve to an EJB that exposes local interfaces.

Cause

The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action

Ensure that the target of the ejb-link is indeed the EJB you would like to refer to. If this is true, you can either add component interfaces to this EJB that are compatible with the ref type or you can change the ref type to be compatible with the interfaces exposed by the target EJB.

BEA-160095

Warning: Warning: The ejbRefType 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' has an invalid interfaceType element value 'invalidInterfaceName'. The target bean does not declare that interfaceType interface. Please ensure the values are correct.

Description

The specified component or home interface name in the ejb-ref or ejb-local-ref declaration does not match the name of the component or home interface of the target EJB. If the ejb-ref is to a business interface, the ejb-ref will fail to resolve at runtime.

Cause

The home or component interface name in the ejb-ref or ejb-local-ref does not match the home or component interface name of the target EJB.

Action

Ensure that the target of the ejb-link is indeed the EJB you would like to refer to. If this is true, fix the ejb-ref or ejb-local-ref so the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.

BEA-160096

Warning: Warning: The ejbRefType 'ejbRefName' in the module 'moduleURI' has an invalid interfaceType element value 'invalidInterfaceName'. The target bean does not declare that interfaceType interface. Please ensure the values are correct.

Description

The specified component or home interface name in the ejb-ref or ejb-local-ref declaration does not match the name of the component or home interface of the target EJB. If the ejb-ref is to a business interface, the ejb-ref will fail to resolve at runtime.

Cause

The home or component interface name in the ejb-ref or ejb-local-ref does not match the home, component or business interface name of the target EJB.

Action

Ensure that the target of the ejb-link is indeed the EJB you would like to refer to. If this is true, fix the ejb-ref or ejb-local-ref so the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.

BEA-160097(retired)

Error: Unable to parse the file 'fileName' because it uses a Java encoding name instead of an IANA encoding name. The Java encoding name used by this file, 'badEncodingName' has an IANA equivalent named 'equivalentIANAEncoding'. Please update the encoding name in the descriptor to be 'equivalentIANAEncoding'.

Description

The specified deployment descriptor uses an invalid XML encoding name. All deployment descriptors must use an IANA encoding name. Fortunately, the encoding used by the descriptor does have an IANA equivalent. Changing the encoding of the descriptor to the recommended encoding name will fix this problem.

Cause

Then encoding used by the deployment descriptor is not supported.

Action

Change the encoding of the deployment descriptor to a supported encoding. The error message suggests what encoding should be used.

BEA-160098

Error: Unable to parse the file 'fileName' because it uses an invalid encoding name, 'badEncodingName'. All deployment descriptors must use an IANA or Java encoding name. Please change the encoding of the descriptor to be a supported encoding.

Description

The specified deployment descriptor uses an invalid XML encoding name. All deployment descriptors must use an IANA or Java encoding name. Changing the encoding of the descriptor to an IANA or Java encoding name will fix this problem.

Cause

Then encoding name used by the deployment descriptor is not supported.

Action

Change the encoding name of the deployment descriptor to an IANA or Java encoding name.

BEA-160099(retired)

Error: Failed to undeploy security role for resource: resource while undeploying the application.

Description

Failed to undeploy security role for resource: resource while undeploying the application.

Cause

The security role defined in application.xml failed to undeploy upon application undeployment.

Action

Check the exception for the exact cause of the problem.

BEA-160100

Error: Could not deploy role: role for application: app.

Description

Could not deploy role: role for application: app.

Cause

The application could not deploy the role defined in application.xml.

Action

Make sure the security is configured properly in the server. Also check the stack trace for the exact cause.

BEA-160101

Error: Error: The ejb-link 'ejbLink' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the application module 'jarName' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.

Description

This ejb-link could not be resolved. If this is a qualified link, first ensure that the application module refereed to by the link exists. Then ensure that that module contains an EJB with the given name. If the link is unqualified, make sure an EJB with an ejb-name equal to the ejb-link value exists in the application. Also, ensure the ejb-link points to an EJB with component interfaces. For example, a message-driven bean is not a valid ejb-link target.

Cause

The target of the ejb-link could not be found in the application.

Action

Fix the ejb-link to point to a valid EJB.

BEA-160102(retired)

Error: Error: The ejb-link 'ejbLink' declared in the ejb-ref or ejb-local-ref 'ejbRefName' in the application module 'jarName' could not be established. The target of the ejb-link does not have a homeType interface. Please ensure the link is correct.

Description

The ejb-link in this ejb-ref or ejb-local-ref resolves to a bean that does not have interfaces compatible with the ref type. For example, an ejb-ref must resolve to an EJB that exposes remote interfaces. Similarly, an ejb-local-ref must resolve to an EJB that exposes local interfaces.

Cause

The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action

Ensure that the target of the ejb-link is indeed the EJB you would like to refer to. If this is true, you can either add component interfaces to this EJB that are compatible with the ref type or you can change the ref type to be compatible with the interfaces exposed by the target EJB.

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. If the .wlnotdelete directory has been deleted or write protected, the server will not be able to write temporary files. Ensure that this directory exists and the server is able to write to it.

BEA-160104

Error: Invalid local reference in application appName. A local reference from module modName to ejbLink is not allowed because the referencing module does not have visibility to the classes of the referenced module.

Description

You can only use an EJB local reference if the classloader organization is such that the calling module can see the classes of the module containing the EJB being called.

Cause

The current module does not have visibility to the classloader of the EJB being referenced.

Action

Look at the classloader organization defined by the classloader-structure element in weblogic-application.xml and make sure that the calling module is either using the same classloader as the module containing the referenced EJB or that the calling module is using a classloader that is an offspring of the classloader of the EJB module.

The compiler was unable to copy files to the specified directory. When an archive is specified as the argument to appc, the compiler must extract the archive to a directory for processing. An error occurred while extracting the jar file to the specified directory. Please make sure the specified directory is writable. Alternatively, you can manually extract the archive to a directory and specify the directory name as the appc argument instead of the archive.

Cause

The compiler was unable to extract the source archive to a directory. This can be caused by a lack of permission to write to the directory or a lack of disk space.

Action

Make sure the directory is writable and that there is enough free disk space to extract the archive. Alternatively, you can manually extract the archive to a directory and specify the directory name as the appc argument instead of the archive.

BEA-160110

Error: ERROR: Appc could not create the working directory, 'directoryName'. Please ensure that this directory can be created and try again.

Description

Appc was unable to create the specified directory. The directory is necessary for compilation to proceed. Please ensure the directory can be created and try again.

Cause

The specified directory could not be created.

Action

Make sure the directory can be created and try again.

BEA-160111

Error: ERROR: Appc can not write to the working directory, 'directoryName'. Please ensure that you have write permission for this directory and try again.

Description

The specified directory is not writable. Appc must be able to write to the directory for compilation to proceed. Please ensure the directory is writable and try again.

Cause

The specified directory is not writable.

Action

Make sure the directory is writable and try again.

BEA-160112

Error: Error: The directory, 'directoryName', does not contain a valid module. If the directory represents an ear file, it must contain a META-INF/application.xml file. If the directory represents an ejb-jar file, it must contain a META-INF/ejb-jar.xml file. If the directory represents a war file, it must contain a WEB-INF/web.xml file. Please ensure the source directory is a valid module and try again.

Description

Appc could not find a valid module to compile in the specified source directory. If the directory represents an ear file, it must contain a META-INF/application.xml file. If the directory represents an ejb-jar file, it must contain a META-INF/ejb-jar.xml file. If the directory represents a war file, it must contain a WEB-INF/web.xml file.

Error: Error: The source file, 'jarName', is not a valid ejb-jar file. To be valid, it must contain a META-INF/ejb-jar.xml file.

Description

The specified source file is not a valid ejb-jar file. All ejb-jar files must contain a META-INF/ejb-jar.xml file. Appc assumes all source files ending with the .jar suffix are J2EE ejb-jar files. If this file is a different type of file, please rename it appropriately. Note that the location of the standard EJB descriptor must be META-INF/ejb-jar.xml. Any variation in the case of this path name may cause this error to be thrown.

Cause

The specified source file is not a valid ejb-jar file.

Action

Ensure the specified source file is a valid ejb-jar file and try again.

BEA-160114

Error: Error: The source file, 'warName', is not a valid war file. To be valid, it must contain a WEB-INF/web.xml file.

Description

The specified source file is not a valid war file. All war files must contain a WEB-INF/web.xml file. Appc assumes all source files ending with the .war suffix are J2EE war files. If this file is a different type of file, please rename it appropriately. Note that the location of the standard WAR descriptor must be WEB-INF/web.xml. Any variation in the case of this path name may cause this error to be thrown.

Cause

The specified source file is not a valid war file.

Action

Ensure the specified source file is a valid war file and try again.

BEA-160115

Error: Error: The source file, 'earName', is not a valid ear file. To be valid, it must contain a META-INF/application.xml file.

Description

The specified source file is not a valid ear file. All ear files must contain a META-INF/application.xml file. Appc assumes all source files ending with the .ear suffix are J2EE ear files. If this file is a different type of file, please rename it appropriately. Note that the location of the standard application descriptor must be META-INF/application.xml. Any variation in the case of this path name may cause this error to be thrown.

Cause

The specified source file is not a valid ear file.

Action

Ensure the specified source file is a valid ear file and try again.

BEA-1601BEA-16(retired)

Error: Error: The source file, 'fileName', contains multiple modules. Only a single ejb-jar, war or ear file can be specified as a source file for appc. If this source file represents an ear file, it must contain a META-INF/application.xml file. Please fix the source argument and try again.

Description

The specified source file contains multiple modules but is not a valid ear file. Only a single ejb-jar, war or ear file can be specified as a source file for appc. Please fix the source file and try again.

Cause

The specified source file contains multiple modules but is not a valid ear file.

Action

Ensure the specified source file contains a single module or is a valid ear file.

BEA-160117

Error: Appc is unable to continue processing file 'fileName':\nerror

Description

An error occurred while processing the specified source file. The message should contain details of the error.

Cause

An error occurred while processing the specified source file.

Action

Find the cause of the exception and take any necessary steps to remedy it.

BEA-160118

Error: Appc is unable to continue processing the file 'fileName'. The following error occurred while accessing it:\nerror

Description

An error occurred while processing the specified source file. The message should contain details of the error.

Cause

An error occurred while processing the specified source file.

Action

Find the cause of the exception and take any necessary steps to remedy it.

BEA-160119

Error: Appc is unable to process the file 'fileName'. The following error occurred:\nerror

Description

An error occurred while processing the specified source file. The message should contain details of the error.

Cause

An error occurred while processing the specified source file.

Action

Find the cause of the exception and take any necessary steps to remedy it.

BEA-160120

Error: Error: The module, 'moduleURI', is declared either in the application.xml or in the weblogic-application.xml descriptor but cannot be found in the ear file.

Description

The specified module is declared either in the application.xml or in the weblogic-application.xml of the ear file passed to appc but the module cannot be found.

Cause

The specified module cannot be found in the ear file.

Action

Ensure that either application.xml or weblogic-application.xml declaration is correct.

BEA-160121

Error: Errors encountered while compiling module 'moduleURI':\nerrors

Description

Errors were encountered while the specified module was being compiled. Details of the specific errors should follow the message.

Cause

Errors were encountered while compiling the specified module.

Action

Investigate the specific errors and take any recommended actions.

BEA-160122

Error: Errors validating ear file:\nerrors

Description

Errors were encountered while the ear file was being validated. Details of the specific errors should follow the message.

Appc encountered an error while attempting to create the output archive. The output archive is created by archiving the appc working directory after compilation has completed. Since a file already existed with the same name as the output archive, the old file will be restored.

Appc encountered an error while attempting to create the output archive. The output archive is created by archiving the appc working directory after compilation has completed.

Cause

An error occurred while creating the output archive.

Action

Investigate the specific error and take any necessary actions.

BEA-160125

Error: ERROR: Could not delete old backup file: fileName

Description

Appc was unable to delete the specified backup archive. Backup archives are created to ensure an appc failure will not result in the loss of a source file. This failure occurred when appc was attempting to backup an archive to the specified file name. An old backup file already existed with the same name but appc was unable to remove it.

Cause

An old backup file could not be removed.

Action

Determine why the old backup file could not be deleted and remedy the problem. Manually deleting the old backup file prior to running appc should fix this.

Appc was unable to create the specified backup archive. Backup archives are created to ensure an appc failure will not result in the loss of a source file. This failure occurred when appc was attempting to backup an archive to the specified file name.

Cause

The specified backup file could not be created.

Action

Determine why the backup file could not be created and remedy the problem. In particular, ensure you have write permission to the specified file and that your disk is not full.

BEA-160127

Error: ERROR: Could not delete previous archive: fileName

Description

Appc was unable to delete the specified archive. This archive must be removed so an updated archive can be written in its place.

Cause

The specified archive could not be removed.

Action

Determine why the archive could not be deleted and remedy the problem. In particular, ensure you have permission to modify the specified file.

BEA-160128

Error: ERROR: Incorrect appc command-line. Too many arguments were given. The command-line only takes a single argument, the source file, in addition to the supported options.

Description

The appc command-line should consist of a single argument, the source file, along with any supported options. The command line specified contained more than one argument.

Cause

Too many arguments were specified on the command line.

Action

Correct the command line and try again.

BEA-160129

Error: ERROR: The alt-dd 'altDD', specified for application module 'moduleURI', could not be found. Please remove the alt-dd entry from the application.xml descriptor or ensure it points to a valid deployment descriptor.

Description

The application.xml deployment descriptor for this ear file specifies an alt-dd element that can not be found. The alt-dd setting must point to a valid deployment descriptor in the ear file. The error message contains the specific alt-dd that could not be found along with the URI of the module the alt-dd was specified for.

Cause

The specified alt-dd could not be found.

Action

Remove the invalid alt-dd entry from application.xml or ensure it points to a valid deployment descriptor.

BEA-160130

Error: ERROR: The application level alt-dd 'altDD', specified on the appc command line, could not be found. Please ensure the alt-dd points to a valid deployment descriptor or remove it from the command line.

Description

An application level alt-dd file was specified on the appc command line but the file could not be found. The alt-dd setting must point to a valid deployment descriptor. The error message contains the specific alt-dd that could not be found.

Cause

The specified alt-dd could not be found.

Action

Correct or remove the invalid alt-dd setting on the appc command line.

Applications can be deployed via the admin console or weblogic.deploy too l.

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. Check your server log for errors.

BEA-160132

Warning: Warning: The refType 'ejbRefName' for EJB 'ejbName' in the module 'moduleURI' has an ejb-ref-type of ejbRefType but the ejb-link does not resolve to an EJB of that type. Please ensure the ejb-link and ejb-ref-type are correct.

Description

The specified ejb-ref or ejb-local-ref has an ejb-ref-type that does not match the type of EJB the ejb-ref resolves to. Although the EJB container does not use the ejb-ref-type, this discrepency is pointed out to ensure the ejb-link is indeed pointing to the correct EJB.

Cause

The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action

Ensure the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, make sure the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.

BEA-160133

Warning: Warning: The refType 'ejbRefName' in the module 'moduleURI' has an ejb-ref-type of ejbRefType but the ejb-link does not resolve to an EJB of that type. Please ensure the ejb-link and ejb-ref-type are correct.

Description

The specified ejb-ref or ejb-local-ref has an ejb-ref-type that does not match the type of EJB the ejb-ref resolves to. This discrepency is pointed out to ensure the ejb-link is indeed pointing to the correct EJB.

Cause

The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action

Ensure the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, make sure the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.

BEA-160134

Warning: Error: The EJB with the name 'ejbName' in ear module 'moduleURI' has an entity-cache-ref with the name 'cacheName' in its weblogic-ejb-jar.xml descriptor but no application level entity cache with that name is defined in the weblogic-application.xml descriptor for the application.

Description

The specified EJB refers to an unknown entity-cache in its weblogic-ejb-jar.xml descriptor. Please make sure the entity-cache-ref is correct in the weblogic-ejb-jar.xml for the EJB. Also, ensure an entity-cache with the same name is declared in the weblogic-application.xml descriptor for the application.

Cause

The entity-cache referred to by the EJB could not be found.

Action

Ensure entity-cache-ref is correct in the weblogic-ejb-jar.xml descriptor for the EJB. Also, ensure an entity-cache with the same name is declared in the weblogic-application.xml descriptor for the application.

BEA-160135(retired)

Warning: There was an error encountered while stopping the application named 'appName'. The error was: th

Description

An unexpected error occurred while stopping the application.

Cause

Please consult the nested exception for details on the error.

Action

Correct the situation causing the nested exception and redeploy the application.

BEA-160136(retired)

Error: Cannot use a JMS destination because the object is of the wrong type

Description

A JMS destination is either a Queue when a Topic was expected, or vice versa, or the object is of neither type.

Cause

Change the application to use a valid destination type.

Action

Change the application to use a valid destination type.

BEA-160137

Error: Error: The message-destination-link 'destLink' declared in the message-destination-ref 'destRefName' in the application module 'jarName' could not be resolved. The target message-destination for the message-destination-ref could not be found. Please ensure the link is correct.

Description

This message-destination-link could not be resolved. If this is a qualified link, first ensure that the application module refereed to by the link exists. Then ensure that that module contains a message-destination with the given name. If the link is unqualified, make sure a message-destination with a message-destination-name equal to the message-destination-link value exists in the application.

Cause

The target of the message-destination-link could not be found in the application.

Action

Fix the message-destination-link to point to a valid message-destination.

BEA-160138

Error: Could not set active version state for application: app.

Description

Could not set active version state for application: app.

Cause

Internal error.

Action

Contact Oracle Customer Support.

BEA-160139

Notice: The following library reference has "context-path" set, which has no effect when referencing a lType library: lRef.

Description

The following library reference has "context-path" set, which has no effect when referencing a lType library: lRef. The "context-path" element may only be used when referencing a WAR library.

Cause

The library reference has "context-path" set, but is not referencing a WAR library.

Action

Remove "context-path" from the library reference.

BEA-160140

Warning: Unresolved optional package references (in META-INF/MANIFEST.MF): unresolvedOptionalPackages. Make sure the referenced optional package has been deployed as a library.

Description

Unresolved Optional package references: unresolvedOptionalPackages. Required Optional Packages are declared in MANIFEST.MF files, and reference pre-registered, library jar files. The src path given is informational only, and may point to internal directories that should not be edited. Instead, edit your deployment unit.

Cause

One or more MANIFEST.MF files contain references to Optional Packages (using the Extension-List attribute). One or more of the referenced Optional Packages are not available.

Action

Register the required Optional Packages, or remove the reference(s) from the manifest(s).

Could not initialize the library libInfo. Please ensure the deployment unit is a valid library type (war, ejb, ear). exception

Cause

Caught exception exception.

Action

Examine stacktrace.

BEA-160142

Error: The library at location has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1

Description

The library at location has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1

Cause

Cannot parse the Specification-Version for the library at location.

Action

Fix the library"s Specification-Version to conform to the required version string syntax.

BEA-160143

Error: Library libInfo has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Description

Library libInfo has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause

The library cannot be statically deployed because its MBean has an invalid Specification-Version.

Action

Undeploy the library, and deploy it again with a correct Specification-Version.

BEA-160144

Error: Failed to register library libInfo: message.

Description

Failed to register library libInfo: message.

Cause

The error is: message.

Action

Examine the error message.

BEA-160145

Error: Failed to deploy library libInfo, because of conflicting library Manifest values, and library information registered with the server: message. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.

Description

Failed to deploy library libInfo, because of conflicting library Manifest values, and library information registered with the server: message. Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.

Cause

Conflict between library Manifest values, and library settings in the LibraryMBean.

Action

Check the library"s MANIFEST.MF file, and correct version info there to match server settings. Or undeploy the misconfigured library.

BEA-160146

Error: Failed to process library at location, because of conflicting library Manifest values, and library information provided on the appc command line: message.

Description

Failed to process library at location, because of conflicting library Manifest values, and library information provided on the appc command line: message.

Do not set library name/version info on the appc command line if its already set in the Manifest, or, remove values from Manifest and set them on the appc command line.

BEA-160147

Error: One or more libraries could not be processed. See error above.

Description

One or more libraries could not be processed. See error above.

Cause

See error above.

Action

See error above.

BEA-160148

Info: These libraries were not referenced by the compiled application: libraries.

Description

These libraries were not referenced by the compiled application: libraries.

Cause

Libraries that were passed to appc were not referenced by the compiled application.

Action

These libraries do not need to be passed to appc to compile this particular application.

BEA-160149

Error: Error while processing library references. error.

Description

Error while processing library references. error.

Cause

The application has library references that do not resolve.

Action

Ensure the library references are accurate, and that the required libraries are available.

BEA-160150

Error: A library reference in weblogic-application.xml has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1

Description

A library reference in weblogic-application.xml has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1

Cause

Cannot parse the Specification-Version of a library reference in weblogic-application.xml

Action

Fix the library"s Specification-Version in weblogic-application.xml to conform to the required version string syntax.

BEA-160151

Info: Registered library info.

Description

Registered library info.

Cause

Library registration was successful.

Action

No action required.

BEA-160152

Error: The library at location was not recognized as a valid library type.

Description

The library at location was not recognized as a valid library type.

Cause

The library at location was not recognized as a valid library type.

Action

Make sure the library is one of the supported library types.

BEA-160153

Warning: Error while cleaning up library libraryInfo: exception

Description

Error while cleaning up library libraryInfo: exception

Cause

Error while cleaning up library libraryInfo: exception

Action

Examine the stacktrace.

BEA-160154

Error: Error while cleaning up library: libraryInfo. \nexception

Description

Error while cleaning up library: libraryInfo. \nexception

Cause

Error while cleaning up library: libraryInfo. \nexception

Action

Examine the stacktrace.

BEA-160155

Error: Cannot find library at: location.

Description

Cannot find library at: location.

Cause

location is not a file.

Action

Fix path to library.

BEA-160156

Error: Cannot process libdir: dir is not a directory.

Description

Cannot process libdir: dir is not a directory.

Cause

dir is not a directory.

Action

Fix path to libdir.

BEA-160157

Error: The referenced library, library, is not a supported application library.

Description

The referenced library, library, is not a supported application library.

Cause

library is not a supported application library.

Action

Remove the reference to library library from weblogic-application.xml.

BEA-160158

Warning: Ignoring Extension-List reference name, because the Manifest does not have an entry for name-Extension-Name. The Manifest is at src/META-INF/MANIFEST.MF

Description

Ignoring Extension-List reference name, because the Manifest does not have an entry for name-Extension-Name. The Manifest is at src/META-INF/MANIFEST.MF

Cause

A declared Extension-List name does not have the required Extension-Name entry.

Action

Remove name from the Extension-List, or add an name-Extension-Name entry into the Manifest.

Bad Optional Package reference in Manifest at src/META-INF/MANIFEST.MF, for Optional Package with Extension-Name: name. Illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1. Ignoring this Optional Package reference.

Cause

Cannot parse the Specification-Version of an Optional Package reference.

Action

Fix the Optional Package reference Specification-Version to the required version string syntax.

BEA-160BEA-160(retired)

Warning: The role mappings for these roles, defined in weblogic-application.xml, are not referenced from application.xml: roles.

Description

The role mappings for these roles, defined in weblogic-application.xml, are not referenced from application.xml: roles.

Cause

There are role mappings defined in weblogic-application.xml that are not referenced from weblogic.xml.

Action

Remove the unreferenced role mappings from weblogic-application.xml.

BEA-160BEA-161

Warning: Error while parsing the Application descriptors for ear: error.

Description

Error while parsing the Application descriptors for ear: error.

Cause

The cause is error.

Action

Examine error message.

BEA-160BEA-162

Warning: No META-INF/application.xml was found in the EAR at ear.

Description

No META-INF/application.xml was found in the EAR at ear.

Cause

Could not find application.xml.

Action

Make sure path to ear is correct, add missing application.xml.

BEA-160BEA-163

Warning: No modules found in application.xml for ear: ear. Nothing to do.

Description

No modules found in application.xml for ear: ear. Nothing to do.

Cause

There are no modules in this ear"s application.xml

Action

Add module entries to the ear"s application.xml.

BEA-160BEA-164

Error: Error while importing library lib: ex.

Description

Error while importing library lib: ex.

Cause

See Exception: ex.

Action

Examine stacktrace.

BEA-160BEA-165

Error: The EAR library at location is organized using the splitdir directory structure. splitdir is not supported for libraries.

Description

The EAR library at location is organized using the splitdir directory structure. splitdir is not supported for libraries.

Cause

splitdir is not supported for EAR libraries.

Action

Archive this library. If you generated a build file using BuildXMLGen, run the ear target in that file.

BEA-160BEA-166

Info: References were found in deployment plan for module 'name' with uri, 'uri'. The plan was merged.

Description

A deployment plan is associated with the application may include overrides for the indicated module.

Cause

The plan contained variable overrides

Action

No action: this is an informational message.

BEA-160BEA-167

Error: The module modName in application appName uses ejb-links but no EJB modules were found for this application.

Description

The module modName in application appName uses ejb-links but no EJB modules were found for this application.

Cause

The ejb-links must correspond to an EJB module deployed within the same application.

Action

Make sure the EJB modules you intended to link to exist and have been configured properly.

BEA-160BEA-168

Error: An error occurred while merging descriptors:\nstacktrace

Description

An error occurred while merging descriptors:\nstacktrace

Cause

Check stacktrace.

Action

Check stacktrace.

BEA-160BEA-169

Error: An error occurred while parsing descriptors:\nstacktrace

Description

An error occurred while parsing descriptors:\nstacktrace

Cause

Check stacktrace.

Action

Check stacktrace.

BEA-160170

Info: Imported library library for Application appName

Description

Imported library library for Application appName

BEA-160171

Error: ERROR: The plan file, 'sourceName', could not be found.

Description

The plan file, specified in the appc command-line, could not be found. Please make sure the file exists and try again.

Cause

The plan file could not be found.

Action

Make sure the specified plan file exists and try again.

BEA-160172

Error: ERROR: You must specify a plan file ending with the suffix .xml run appc.

Description

The plan file, specified in the appc command-line, is not a supported file type. Please correct the plan argument and try again.

Cause

The plan file type is not supported.

Action

Correct the command-line plan argument and try again.

BEA-160173

Error: ERROR: Error accessing input file 'sourceName':\nerror

Description

The plan file, specified in the appc command-line, is not accessible. Please make sure you have read permission for the file.

Cause

The plan file could not be accessed.

Action

Make sure the plan file is accessible and try again.

BEA-160174

Error: ERROR: Failed to parse deployment plan 'sourceName':\nerror

Description

The plan file, specified in the appc command-line, is invalid.

Cause

The plan file could not be parsed.

Action

Resolve parse errors in plan and retry.

BEA-160175

Error: ERROR: Could not find JMS module of name "moduleName" specified in the resource-link named "resLinkName" in the "appComponentType" component named "appComponentName".

Description

JMS module used in the resource-link is not found in the application package.

Cause

JMS module used in the resource-link is not found in the application package.

Action

Package the missing JMS module as part of this application and retry.

BEA-160176

Error: ERROR: Could not find the JMS resource named "resourceName" of type "resType" inside the JMS module "moduleName" that is specified in the resource-link named "resLinkName" in the "appComponentType" component named "appComponentName".

Description

JMS resource used in the resource-link is not found in the application package.

Cause

JMS resource used in th resource-link is not found in the application package.

Action

Create the missing JMS resource in the corresponding JMS module and retry.

BEA-160177

Error: The application at "path" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, please consult the WebLogic Server documentation.

Warning: The user attempted to stop the modules with uris: uris, but no modules were found in the application with these uris. Note that if you are trying to stop a Web Application, you should specify the context-root rather than the web-uri.

Description

Partial stop action did not match any running modules.

Cause

The specified uris were not found in the running application.

Action

Specify the correct uris which are typically found in your application"s META-INF/application.xml.

BEA-160179(retired)

Warning: An error was encountered and ignored while stopping application appId. The error was: e

Description

An error was encountered and ignored while stopping the application.

Cause

See the included error message.

Action

Correct the application.

BEA-160180

Warning: An error was encountered and ignored while rolling back an update to application appId. The error was: th

Description

An error was encountered and ignored while updating the application.

Cause

See the included error message.

Action

Correct the application.

BEA-160181

Warning: An error was encountered and ignored during undeployment. The error was: th

Description

An error was encountered and ignored while undeploying the application.

Cause

See the included error message.

Action

Correct the application.

BEA-160182

Warning: An error was encountered and ignored during transition to admin-mode. The error was: th

Description

An error was encountered and ignored while moving to admin-mode.

Cause

See the included error message.

Action

Correct the application.

BEA-160183

Error: Unable to find the jar-uri: uri specified for the ApplicationLifecycleListener, Startup, or Shutdown class in the weblogic-application.xml of application: appId

Description

Unable to locate the jar file for the ApplicationLifecycleListener.

Cause

The jar uri is incorrect, or the file does not exist or cannot be read.

Action

Correct the application.

BEA-160184

Error: ERROR: Could not find JDBC module of name "moduleName" specified in the resource-link named "resLinkName" in the "appComponentType" component named "appComponentName".

Description

JDBC module used in the resource-link is not found in the application package.

Cause

JDBC module used in the resource-link is not found in the application package.

Action

Package the missing JDBC module as part of this application and retry.

BEA-160185

Error: ERROR: Could not find the JDBC resource named "resourceName" of type "resType" inside the JDBC module "moduleName" that is specified in the resource-link named "resLinkName" in the "appComponentType" component named "appComponentName".

Description

JDBC resource used in the resource-link is not found in the application package.

Cause

JDBC resource used in th resource-link is not found in the application package.

Action

Create the missing JDBC resource in the corresponding JDBC module and retry.

BEA-160186

Info: Compiling EAR module 'uri'

Description

The specified ear module is now being compiled by appc.

Cause

None

Action

None

BEA-160187

Error: weblogic.appc failed to compile your application. Recompile with the -verbose option for more details. Please see the error message(s) below.

Description

An unexpected exception was thrown while compiling your application. Rerunning appc with the -verbose option will provide you with more information about the failure.

Cause

Compilation can fail for many reasons. See the specific error message for details.

Action

Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic, please contact support.

BEA-160188

Warning: s.

Description

s.

Cause

The application has library references that do not resolve.

Action

Ensure the library references are accurate, and that the required libraries are available.

BEA-160189

Error: There are no modules in the application that match uri(s): uris. Note that for Web Applications, you should specify the context-root rather than the web-uri.

Description

The partial stop/redeploy action did not match any running modules.

Cause

The specified uris were not found in the running application.

Action

Specify the correct uris which are typically found in your application"s META-INF/application.xml.

BEA-160190(retired)

Warning: The JMS connection pool named "poolName" has a configured connection factory JNDI name of "jndiName". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "clazz".

Description

The JMS connection pool named "poolName" has a configured connection factory JNDI name of "jndiName". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "clazz".

Cause

An object other than a ConnectionFactory is bound to the configured JNDI name of the connection pool.

Action

Either change the JNDI name of the JMS connection pool property or change the JNDI name of the object that is currently bound into JNDI.

BEA-160191

Info: While upgrading weblogic.xml, encountered "parentName" param "paramName". This param has been deprecated and will be removed

Description

While upgrading weblogic.xml, encountered "parentName" param "paramName". This param has been deprecated and will be removed

Cause

Deprecated param.

Action

Remove deprecated param from weblogic.xml deployment descriptor.

BEA-160192

Info: While upgrading weblogic.xml, encountered "parentName" param "paramName". This param is unknown and will be removed

Description

While upgrading weblogic.xml, encountered "parentName" param "paramName". This param is unknown and will be removed

Cause

The param is not defined in the schema.

Action

Check weblogic.xml deployment descriptor, remove param.

BEA-160193

Error: Error: The source file, 'rarName', is not a valid rar file. To be valid, it must contain a META-INF/ra.xml file.

Description

The specified source file is not a valid rar file. All rar files must contain a META-INF/ra.xml file. Appc assumes all source files ending with the .rar suffix are J2EE rar files. If this file is a different type of file, please rename it appropriately. Note that the location of the standard RAR descriptor must be META-INFO/ra.xml. Any variation in the case of this path name may cause this error to be thrown.

Cause

The specified source file is not a valid rar file.

Action

Ensure the specified source file is a valid rar file and try again.

BEA-160194

Error: The following modules cannot be started because they are already running: uris.

Description

Module(s) cannot be partially started if they are already running.

Cause

The specified modules are already running.

Action

Remove the specified modules from the list of modules to partially stop.

BEA-160195

Warning: The application version lifecycle event listener listenerClass is ignored because the application app is not versioned.

Description

Application version lifecycle listeners are only enabled for versioned applications.

Cause

The application is not a versioned application.

Action

If the application is deployed as a non-versioned application in error, undeploy the current application and deploy it as a versioned application. If the application version lifecycle listener is specified in error, remove it from the application or specify a non-versioned application lifecycle listener.

BEA-160196

Error: Unable to find the jar-uri: uri specified for the Singleton class in the weblogic-application.xml of application: appId

Description

Unable to locate the jar file for the Singleton service.

Cause

The jar uri is incorrect, or the file does not exist or cannot be read.

Action

Correct the application.

BEA-160197

Error: Unable to load descriptor path of module moduleName. The error is stackTrace.

Description

Unable to load descriptor

Cause

The descriptor is not valid.

Action

Correct the descriptor.

BEA-160198

Error: Error: The ejb-ref 'ejbRefName' configured via an @EJB annotation in the module 'moduleUri' is linked to the EJB 'targetEJB'. However, the EJB 'targetEJB' does not declare the interface 'interfaceName', as specified by the @EJB annotation. Please ensure the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.

Description

There was a problem validating the ejb-ref configured via an @EJB annotation in the module specified.

Cause

The @EJB has an incorrect beanName (ejb-link) attribute or the target bean must implement the interface declared by the @EJB annotation.

Action

Correct the application.

BEA-160199

Error: Error resolving ejb-ref 'ejbRefName' from module 'moduleName' of application 'applicationName'. The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because multiple EJBs in the application were found to implement the 'interfaceName' interface. Please specify a qualified ejb-link for this ejb-ref to indicate which EJB is the target of this ejb-ref.

Description

There was a problem resolving the target of the specified ejb-ref.

Cause

See the error message for details.

Action

Correct the application.

BEA-160200

Error: Error resolving ejb-ref 'ejbRefName' from module 'moduleName' of application 'applicationName'. The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the 'interfaceName' interface. Please link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.

Description

There was a problem resolving target of the specified ejb-ref.

Cause

See the error message for details.

Action

Correct the application.

BEA-160201

Error: Error resolving ejb-ref 'ejbRefName' from module 'moduleName' of application 'applicationName'. The ejb-ref specifies an ejb-link but the target bean does not implement the interface 'interfaceName' as specified in the ejb-ref declaration. Please ensure the ejb-link and interface name(s) declared in the ejb-ref are correct.

Description

There was a problem resolving target of the specified ejb-ref.

Cause

See the error message for details.

Action

Correct the application.

BEA-160202

Warning: You have specified a confKey setting in your configuration for persistence unit puId. This setting will be ignored, and all log messages will be sent to the WebLogic logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings in config.xml, or via the WebLogic console.

Error: The ApplicationLifecycleListener 'listener' of application 'applicationName' has a run-as user configured with the principal name 'principalName' but a principal of that name could not be found. Please ensure a user with that name exists.

Description

The run-as principal configured for this ApplicationLifecycleListener does not exist in the security realm. Ensure the user exists or choose another principal for the run-as configuration.

Cause

See the error message body.

Action

See the error message body.

BEA-160205

Error: The ApplicationLifecycleListener 'listener' of application 'applicationName' has a run-as user configured with the principal name 'principalName' but a principal of that name has higher privileges than the user performing the deployment. Hence this deployment user cannot perform the current deployment action. Try the deployment action with admin privileged user.

Description

We detected a situation where a user tried to deploy an ApplicationLifecycleListener with run-as privileges set higher than the privileges of the user performing the deployment. This is disallowed and the deployment failed.

Cause

See the error message body.

Action

See the error message body.

BEA-160206

Debug: The OpenJPA persistence unit 'puName' uses an application-provided version of OpenJPA instead of the WebLogic-provided version. This will impact the integration of your persistence unit with WebLogic, and will prevent this persistence unit from using Kodo features.

Description

See message body.

Cause

This is probably happening as a result of configuring your enterprise archive to filter out WebLogic-provided org.apache.openjpa classes, via the deployment descriptor element.

Action

No action is necessary.

BEA-160207

Error: Error autowiring ejb-ref 'ejbRefName' from module 'moduleName' of application 'applicationName'. The ejb-ref does not specify an interfaceName but multiple interfaces on the target bean were found. Please specify an beanInterface to indicate which EJB is the target for ejb-ref 'ejbRefName'.

Description

There was a problem resolving the target of the specified ejb-ref.

Cause

See the error message for details.

Action

Correct the application.

BEA-160208(retired)

Error: Only WAR library can be auto-reference library.

Description

Only WAR library can be auto-reference library.

Cause

See the error message for details.

Action

Please use WAR library as auto-reference library.

BEA-160209(retired)

Error: Only one auto-reference library can be deployed.

Description

Only one auto-reference library can be deployed.

Cause

See the error message for details.

Action

Please deploy only one library as auto-reference library.

BEA-160210

Error: ERROR: The moduleUri, 'moduleUri', could not be found.

Description

The moduleUri, specified in the appc command-line, could not be found. Please make sure the module exists and try again.

Cause

The moduleUri could not be found.

Action

Make sure the specified moduleUri exists and try again.

BEA-160214

Warning: Output location exists loaction

Description

Output location loaction already exists and will be overwritten. The output location may have been either passed into the module or may have been the default value.

Filtering class loader configuration is only supported in descriptors at the main level of the deployment, for example in enterprise applications or standalone web applications. Such configuration is not supported in modules of an enteprise application.

Action

Remove the filtering class laoder configuration from the deployment descriptor of module moduleUri of application appId

BEA-160219

Info: The JPA persistence unit persistenceUnitId will use the following configured default persistence provider: provider

Description

The persistence.xml descriptor associated with the named persistence unit does not have a persistence provider specified. As a result, the configured default provider will be used.

Cause

No provider element specified in associated persistence.xml file.

Action

No action needs to be taken unless you want a different JPA provider to be used for the given persistence unit in which case you can specify the provider in the persistence.xml or change the default provider for the domain.

Your application is invoking a method defined in JPA 2.0 but the persistence provider configured in your application is only JPA 1.0 compliant. Note the deprecated Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.

Cause

Your application is invoking a method defined in JPA 2.0 but the persistence provider configured in your application is only JPA 1.0 compliant. Note the deprecated Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.

Action

Update your application to use a JPA 2.0 compliant persistence provider such as EclipseLink or modify your application to ensure only JPA 1.0 API methods are invoked.