EJB Subsystem Messages

The EJB1.0 catalog contains messages in the range BEA-010000 - BEA-019999. Messages in this catalog are part of the weblogic.ejb.container Internationalization package and the weblogic.ejb.container Localization package.

BEA-010000

Info: Exception occurred during ejbActivate: excep

Description	Exception occurred during ejbActivate: excep
Cause	An error occurred while calling ejbActivate() on the bean.
Action	Check your implementation of the ejbActivate method.

BEA-010001

Warning: While deploying EJB 'ejbName', class className was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.

Description	The specified class was loaded from the system classpath instead of from the ejb-jar file. As a result, the class cannot be dynamically updated while the server is running. Any changes to the class will not take effect until the server is restarted.
Cause	The specified class is located in the server classpath.
Action	Remove this class from the server classpath. It should only be located in the packaged application.

BEA-010002

Error: An error occurred while undeploying:deploymentName.

Description	The exception was: excep
Cause	An error occurred while undeploying.
Action	Please check the exception for the exact error message.

BEA-010003

Error: Exception occurred while loading _WL_TIMESTAMP FILE.

Description	Exception occurred while loading _WL_TIMESTAMP FILE. Forcing recompilation: ioException
Cause	The container generates _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in _WL_GENERATED file, appc recompiles the beans. There was an error reading this file.
Action	The container will automatically recompile the beans.

BEA-010004(retired)

Warning: The EJB deployment named: deploymentName was compiled by a different version of WebLogic Server.

Description	The EJB deployment named: deploymentName was compiled by a different version of WebLogic Server.
Cause	See message body.
Action	It is recommended that you re-run weblogic.appc whenever the server version changes.

BEA-010005(retired)

Warning: Error occurred while reading WebLogic Server-generated files in deployment: deploymentName. Exception is: ioExcep.

Description	Error occurred while reading WebLogic Server-generated files in deployment: deploymentName. Exception is: ioExcep.
Action	Please check the exception for the exact error message. It is recommended that you re-run weblogic.ejbc.

BEA-010006

Error: Error occurred while saving ejb deployment timestamps. ioExcep

Description	Error occurred while saving ejb deployment timestamps. ioExcep
Cause	The container generates _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in _WL_GENERATED file, appc recompiles the beans. There was an error writing this file.
Action	Please check the exception for the exact error message. The container will recompile the beans if this file is not found.

BEA-010007

Info: License validation passed for ejbVersion.

Description

License validation passed for ejbVersion.

BEA-010008

Info: EJB Deploying file: beanFile

Description

EJB Deploying file: beanFile

BEA-010009

Info: EJB Deployed EJB with JNDI name jndiName.

Description

EJB Deployed EJB with JNDI name jndiName.

BEA-010010(retired)

Info: Exception looking up current transaction:\n stackTrace

Description

Exception looking up current transaction:\n stackTrace

BEA-010011

Info: Exception looking up current transaction:\n stackTrace

Description

Exception looking up current transaction:\n stackTrace

BEA-010012

Info: Exception looking up current transaction:\n stackTrace

Description

Exception looking up current transaction:\n stackTrace

BEA-010013(retired)

Warning: EJB "EJBName" referenced an undeclared security role "roleName".

Description

EJB "EJBName" referenced an undeclared security role "roleName".

BEA-010014

Notice: Error occurred while attempting to rollback transaction: excep

Description	Error occurred while attempting to rollback transaction: excep
Cause	There was an error rolling back the transaction.
Action	Please check the exception for the exact error message.

BEA-010015

Notice: Error occurred while marking transaction for rollback: exp.

Description	Error occurred while marking transaction for rollback: exp.
Cause	The container was unable to mark the transaction for rollback.
Action	Please check the exception for exact error message.

BEA-010016

Notice: Exception occurred while marking transaction for rollback: exp.

Description	Exception occurred while marking transaction for rollback: exp.
Cause	The container was unable to mark the transaction for rollback.
Action	Please check the exception for exact error message.

BEA-010017

Notice: Exception occurred during rollback of transaction transaction: stackTrace.

Description	Exception occurred during rollback of transaction transaction: stackTrace.
Cause	The container was unable to rollback the transaction.
Action	Please check the exception for the exact error message.

BEA-010018

Notice: Error occurred while resuming caller transaction: excep

Description	Error occurred while resuming caller transaction: excep
Cause	The container was unable to resume the transaction.
Action	Please check the exception for the exact error message.

BEA-010019

Warning: Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.

Description	Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.
Cause	DNS name of cluster is not set.
Action	Set DNS cluster name.

BEA-010020

Error: EJB-20 - MessageDriven - Could not start the JMS connection: excep

Description	There was an error while connecting to JMS in an attempt to receive messages for a message-driven bean.
Cause	The JMS provider may not be available, or the message-driven bean deployment descriptors and/or annotation may not be correct.
Action	Verify that the JMS provider is running and accessible through the network. Verify that the deployment descriptors and/or annotation specify the correct configuration information for the JMS provider.

BEA-010021

Error: Clusters must be homogeneous for EJB replication. Please ensure that you have deployed the bean named: jndiName on all members of your WebLogic cluster.

Description	Clusters must be homogeneous for EJB replication. Please ensure that you have deployed the bean named: jndiName on all members of your WebLogic cluster.
Cause	Clusters must be homogeneous for EJB replication.
Action	Please ensure that you have deployed the bean named: jndiName on all members of your WebLogic cluster.

BEA-010022

Error: Error occurred in ejbPassivate: stackTrace.

Description	Error occurred in ejbPassivate: stackTrace.
Cause	There was an error passivating the bean.
Action	Please check the exception for the exact error message. Verify the implementation of ejbPassivate method in the bean.

BEA-010023(retired)

Error: Diskswap - error in setup for StatefulEJBCache:\n stackTrace.

Description	Diskswap - error in setup for StatefulEJBCache:\n stackTrace
Cause	The container is unable to set up the disk for passivating the beans.
Action	Please check the exception for the exact error message

BEA-010024

Error: Error occurred during passivation: stackTrace

Description	Error occurred during passivation: stackTrace
Cause	The container was unable to passivate the bean.
Action	Please check the exception for the exact error message.

BEA-010025

Error: Exception occurred during rollback of transaction transaction: stackTrace

Description	Exception occurred during rollback of transaction transaction: stackTrace
Cause	There was an error rolling back the transaction.
Action	Please check the exception for the exact error message.

BEA-010026

Error: Exception occurred during commit of transaction transaction: stackTrace.

Description	Exception occurred during commit of transaction transaction: stackTrace.
Cause	There was an error committing the transaction.
Action	Please check the exception for the exact error message.

BEA-010027(retired)

Info: Exception occurred during rollback of transaction transaction: stackTrace.

Description	Exception occurred during rollback of transaction transaction: stackTrace.
Cause	There was an error rolling back the transaction.
Action	Please check the exception for the exact error message.

BEA-010028(retired)

Info: Exception occurred during commit of transaction transaction: stackTrace.

Description	Exception occurred during commit of transaction transaction: stackTrace.
Cause	There was an error committing the transaction.
Action	Please check the exception for the exact error message.

BEA-010029

Info: Exception occurred during commit of transaction transaction: stackTrace.

Description	Exception occurred during commit of transaction transaction: stackTrace.
Cause	There was an error committing the transaction.
Action	Please check the exception for the exact error message.

BEA-010030

Info: Ignoring exception that occurred during roll back a transaction during undeployment of homeJNDIName.

Description	Ignoring exception that occurred roll back a transaction during undeployment of homeJNDIName. The exception was: excep
Cause	There was an error undeploying the bean.
Action	Please check the exception for the exact error message.

BEA-010031

Info: EJB Exception in method: MethodName: throwable.

Description	EJB Exception in method: MethodName: throwable.
Action	Please check the exception for the exact error message.

BEA-010032

Info: Exception during ejbActivate(): stackTrace

Description	Exception during ejbActivate(): stackTrace
Action	Please check the exception for the exact error message.

BEA-010033

Info: Exception from ejbLoad: throwable

Description	Exception from ejbLoad: throwable
Action	Please check the exception for the exact error message.

BEA-010034

Info: Exception from ejbStore: throwable.

Description	Exception from ejbStore: throwable.
Action	Please check the exception for the exact error message.

BEA-010035(retired)

Info: EJB Exception occurred during invocation from home: ejbHome and primary key: primKey threw exception: throwable

Description	EJB Exception occurred during invocation from home: ejbHome and primary key: primKey threw exception: throwable
Action	Please check the exception for the exact error message.

BEA-010036

Info: Exception from ejbStore: throwable.

Description	Exception from ejbStore: throwable.
Action	Please check the exception for the exact error message.

BEA-010037(retired)

Info: Exception from ejbLoad: throwable.

Description	Exception from ejbLoad: throwable.
Action	Please check the exception for the exact error message.

BEA-010038

Info: Exception from __WL_superEjbLoad: throwable.

Description	Exception from __WL_superEjbLoad: throwable.
Action	Please check the exception for the exact error message.

BEA-010039

Info: Exception in ejbStore: throwable.

Description	Exception in ejbStore: throwable.
Action	Please check the exception for the exact error message.

BEA-010040

Info: Exception in ejbStore: throwable.

Description	Exception in ejbStore: throwable.
Action	Please check the exception for the exact error message.

BEA-010041(retired)

Info: ERROR creating secondary: namingException.

Description	ERROR creating secondary: namingException.
Action	Please check the exception for the exact error message.

BEA-010042(retired)

Info: ERROR becoming primary server: namingException.

Description	ERROR becoming primary server: namingException.
Action	Please check the exception for the exact error message.

BEA-010043

Info: Exception in ejbActivate: stackTrace.

Description	Exception in ejbActivate: stackTrace.
Action	Please check the exception for the exact error message.

BEA-010044

Info: Exception trying to resume transaction: excep.

Description	Exception trying to resume transaction: excep.
Action	Please check the exception for the exact error message.

BEA-010045

Info: Exception in afterBegin: stackTrace.

Description	Exception in afterBegin: stackTrace.
Action	Please check the exception for the exact error message.

BEA-010046

Info: Exception in beforeCompletion: stackTrace.

Description	Exception in beforeCompletion: stackTrace.
Action	Please check the exception for the exact error message.

BEA-010047

Info: Exception during setRollbackOnly: excep.

Description	Exception during setRollbackOnly: excep.
Action	Please check the exception for the exact error message.

BEA-010048

Info: Exception in afterCompletion: stackTrace.

Description	Exception in afterCompletion: stackTrace.
Action	Please check the exception for the exact error message.

BEA-010049

Info: EJB Exception in method: methodName: throwable.

Description	EJB Exception in method: methodName: throwable.
Action	Please check the exception for the exact error message.

BEA-010050

Info: A stateless session bean with bean-managed transactions must commit or rollback a transaction before the business method completes.

Description	A stateless session bean with bean-managed transactions must commit or rollback a transaction before the business method completes.
Action	Please check the exception for the exact error message.

BEA-010051

Info: EJB Exception occurred during invocation from home: ejbHome threw exception: throwable

Description

EJB Exception occurred during invocation from home: ejbHome threw exception: throwable

BEA-010052(retired)

Warning: An exception occurred while creating the free pool for EJB ejbName. Since this occurred during server start-up, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: remoteException

Description	An exception occurred while creating the free pool for EJB ejbName. Since this occurred during server start-up, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: remoteException
Cause	An exception was thrown while the EJB container was initializing the free pool of bean instances. The root exception should be printed as part of the warning message issued by the EJB container. Check the server log for further details.
Action	If you believe the root exception is due to a temporary condition that will automatically be resolved, no action is required. If this exception was not due to a temporary condition, please fix the cause of the root exception. If changes to your application are required to fix this issue, you will need to redeploy your updated application.

BEA-010053(retired)

Warning: Warning: disregarding principal "prinName"\ mapped to\nrole "roleName" because it is not found in realm "\realmName"\

Description	Warning: disregarding principal "prinName"\ mapped to\nrole "roleName" because it is not found in realm "\realmName"\
Cause	The principal defined in weblogic-ejb-jar.xml was not found in the realm.
Action	Please check if the principal was defined in the realm.

BEA-010054

Warning: EJB Deployment: ejbName has a class className that is in the classpath. This class should only be located in the ejb-jar file.

Description	EJB Deployment: ejbName has a class className that is found in the classpath. This class should only be located in the ejb-jar file.
Cause	className is in the classpath.
Action	Remove this class from the classpath. It should only be in the ejb-jar.

BEA-010055

Error: Could not load the RDBMS deployment descriptor for EJB ejbName from the file fileName. The file was not found in the JAR file jarName.

Description	Could not load the RDBMS deployment descriptor for EJB ejbName from the file fileName. The file was not found in the JAR file jarName.
Cause	fileName is missing from the JAR file.
Action	Please add the missing file in the JAR file.

BEA-010057

Error: Could not find a license for EJB 3.0. Please contact Oracle to get a license.

Description	Could not find a license for EJB 3.0. Please contact Oracle to get a license.
Cause	Unable to get license for EJB3.0.
Action	Contact Oracle to get a license.

BEA-010058

Info: The EJB deployment named: deploymentName is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a stand-alone tool to generate the required classes.

Description

The EJB deployment named: deploymentName is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a stand-alone tool to generate the required classes.

BEA-010059

Error: An Error occurred while attempting to invalidate the target Read-Only Entity EJB: ejbName. The error was:\nmsg

Description	An Error occurred while attempting to invalidate the target Read-Only Entity EJB: ejbName. The error was:\nmsg
Cause	The invalidation of read-only beans failed.
Action	Please check the message for the cause.

BEA-010060

Info: The Message-Driven EJB: ejbName has connected/reconnected to the JMS destination: destName.

Description	The message-driven bean had previously lost its connection to the JMS destination, possibly due to an error, but it has now re-gained its connection.
Cause	The JMS connection has been re-established.
Action	No action required.

BEA-010061

Warning: The Message-Driven EJB: ejbName is unable to connect to the JMS destination: destName. The Error was:\nerrorMsg

Description	The Message-Driven EJB is unable to connect to the JMS destination. The EJB container will automatically attempt to re-establish the connection with the JMS server. This warning may occur during WebLogic Cluster start-up if the JMS destination is located on another server. When the JMS server connection is re-established, the Message-Driven EJB will again receive JMS messages.
Cause	The JMS destination is not available due to a network problem or a problem with the JMS provider, or the configuration information in the MDB deployment descriptor and/or annotation is incorrect. This warning may also occur during WebLogic Cluster start-up if the JMS destination is located on another server.
Action	Check that the JMS provider is running and that network connectivity is available. Also check that the configuration information in the MDB deployment descriptor and/or annotation is correct.

BEA-010062(retired)

Warning: The Message-Driven EJB: ejbName encountered an error while closing its connection to the JMS destination. The error was:\n errorMsg

Description	An error occurred while attempting to close a connection to JMS. This usually happens when the MDB is being undeployed.
Cause	The JMS provider may no longer be available.
Action	Check that the JMS provider is running and is accessible through the network. Take no action if the MDB is being undeployed and retired anyway.

BEA-010063(retired)

Warning: The EJB: ejbName had an setting in its weblogic-ejb-jar.xml. An error occurred while creating these initial bean instances. The error was:\n errorMsg

Description	The EJB: ejbName had an setting in its weblogic-ejb-jar.xml. An error occurred while creating these initial bean instances. The error was:\n errorMsg
Cause	The container was unable to create the initial beans in free pool.
Action	Please check the exception for the exact error message.

BEA-010064(retired)

Info: The EJB: ejbName threw an Exception during undeployment or redeployment of its application. This exception is ignored. The exception was:\n errorMsg.

Description

The EJB: ejbName threw an Exception during undeployment or redeployment of its application. This exception is ignored. The exception was:\n errorMsg.

BEA-010065

Warning: MessageDrivenBean threw an Exception in onMessage(). The exception was:\n e.

Description	The onMessage method for a message-driven bean threw an exception. The server will continue to present messages to this MDB for processing.
Cause	The onMessage method of the message-driven bean may have thrown an exception for a legitimate reason, such as the loss of a database connection. If that is not the case, then the message-driven bean may have a programming error that causes it to throw an unchecked Java exception, such as a NullPointerException.
Action	Unless you are sure that the message-driven bean has thrown the exception on purpose, check the source code to ensure that it does not contain any programming errors that might cause it to throw an unchecked Java exception such as NullPointerException or IndexOutOfBoundsException.

BEA-010066

Info: The Entity EJB:ejbName threw an exception when its unsetEntityContext was called. This error is ignored by the EJB container. The error was:\n errorMsg

Description

The Entity EJB:ejbName threw an exception when its unsetEntityContext was called. This error is ignored by the EJB container. The error was:\n errorMsg

BEA-010067

Info: Exception during ejbRemove: excep

Description

Exception during ejbRemove: excep

BEA-010068(retired)

Error: EJB-20 - MessageDriven - Could not recover JMS session: excep

Description	The message-driven bean encountered an error while recovering a JMS session. This action takes place after an error occurs inside the message-driven bean itself, which causes the server to try to return the current message back to the queue or topic.
Cause	The message-driven bean may have thrown an exception, or there may be a problem with the JMS provider.
Action	Check that the JMS provider is running and accessible through the network. Also, check that the message-driven bean onMessage method does not throw any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.

BEA-010069(retired)

Error: Error occurred while preparing EJB Module : moduleName.

Description	Error occurred while preparing EJB Module : moduleName.
Cause	The deployer was unable to prepare the module.
Action	Please check the exception for the exact error message.

BEA-010070(retired)

Error: Error occurred while activating EJB Module : moduleName.

Description	Error occurred while activating EJB Module : moduleName.
Cause	The deployer was unable to activate the module.
Action	Please check the exception for the exact error message.

BEA-010071

Error: Error occurred while performing Pop of Caller Principal: excep.

Description	Error occurred while performing Pop of Caller Principal: excep.
Cause	This is a possible internal container error.
Action	Double-check the security settings related to the setting run-as roles and principals.

BEA-010072

Error: Error occurred while starting EJB Module : moduleName\nException is : excep

Description	Error occurred while starting EJB Module : moduleName\nException is : excep
Cause	The container was unable to start the EJB module.
Action	Please check the exception for the exact error message.

BEA-010073

Warning: Unable to add the interfaceName interface "className" and any dependent classes to the client-jar since it was loaded from the Classpath.

Description	Unable to add the interfaceName interface "className" and any dependent classes to the client-jar since it was loaded from the Classpath.
Cause	EJB interface and other dependent classes exist in the system classpath.
Action	Please remove the classes from the system classpath.

BEA-010074

Warning: Unable to create the client-jar file due to classes being loaded from the Classpath rather than the input JAR. Please modify your Classpath so it does not contain these classes and try again.

Description	Unable to create the client-jar file due to classes being loaded from the Classpath rather than the input jar. Please modify your Classpath so it does not contain these classes and try again.
Cause	EJB interface and other dependent classes exist in the system classpath.
Action	Please modify your classpath so it does not contain these classes and try again.

BEA-010075

Info: Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.

Description

Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.

BEA-010076

Info: Client-jar "jarName" created.

Description

Client-jar "jarName" created.

BEA-010077(retired)

Error: Error committing a JMS transaction for the message-driven bean mdbName: jmsError\nException is : stack

Description	This message is no longer used.
Cause	This message is no longer used.
Action	This message is no longer used.

BEA-010078(retired)

Error: Error rolling back a JMS transaction for the message-driven bean mdbName: jmsError\nException is : stack

Description	This message is no longer used.
Cause	This message is no longer used.
Action	This message is no longer used.

BEA-010079

Error: An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: error\nThe exception is : stack

Description	When attempting to receive a message for a message-driven bean, an error occurred. This error usually occurs after WebLogic Server has successfully connected to the JMS provider, but it is no longer able to receive any messages.
Cause	The JMS provider for the MDB may have been shut down or crashed, or network connectivity may have been lost.
Action	Check that the JMS provider is available and accessible through the network.

BEA-010080

Error: An error occurred while attempting to process a message inside a message-driven bean: error\nException is : stack

Description	WebLogic Server encountered an error after receiving a message for processing by a message-driven bean and executing the onMessage method for the bean.
Cause	This error usually occurs if the onMessage method of the message-driven bean throws an exception.
Action	Check that the message-driven bean is able to process messages by ensuring that any resources it uses (such as database connections) are available. Check the message-driven bean source code to ensure that it does not have any bugs that cause an exception (such as a NullPointerException) to be thrown.

BEA-010081

Warning: The message-driven bean mdbName was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.

Description	WebLogic Server can only use one thread to process all messages for a topic when a message-driven bean requires container-managed transactions and uses a foreign (in other words, non-WebLogic) JMS provider.
Cause	The nature of the JMS API does not permit this in a standard way.
Action	No action is required. However, if you require better performance for a foreign JMS provider and do not need exactly-once transactional semantics, re-deploy the MDB so that it has a transaction mode of NotSupported.

BEA-010082

Warning: Failed to undeploy security role for resource: resource, while undeploying EJB.

Description	Failed to undeploy security role for resource: resource, while undeploying EJB.
Cause	Unable to remove the role from security layer.
Action	Please check the exception for the exact error message.

BEA-010083

Warning: Failed to undeploy security policy for resource: resource, while undeploying EJB.

Description	Failed to undeploy security policy for resource: resource, while undeploying EJB.
Cause	Unable to remove the policy from security layer.
Action	Please check the exception for the exact error message.

BEA-010084

Info: The message-driven beans are being suspended. This may take a minute or two.

Description	The message-driven beans are being suspended due to a server suspend or shutdown request. This process will continue when the message-driven beans have completed their work. If the message-driven beans are receiving messages from a foreign (non-WebLogic) JMS provider using container-managed transactions, it may take a few minutes for the calls to the foreign JMS providers to complete.
Cause	The server is being suspended or shut down.
Action	No action required.

BEA-010085

Info: The message-driven beans have all been suspended.

Description	The message-driven beans that recently started to be suspended have now been suspended.
Cause	The server is being suspended or shut down.
Action	No action required.

BEA-010086

Info: The deployment unit that contains MessageDrivenBeans: dinfoName is undeployed already. Server cannot start the message driven beans that are part of undeployed unit.

Description	This message informs the user that the server attempted to start some message-driven beans after they were undeployed. The beans will not be started.
Cause	The beans were started after having been undeployed.
Action	No action required.

BEA-010087

Description

BEA-010088

Info: Could not find a license for in-memory replication of the EJB. This feature is disabled;

Description

Could not find a license for in-memory replication of the EJB. This feature is disabled.

BEA-010089

Error: Failed to create copy of bean: ejbName with error: trace.

Description	Failed to create copy of bean: ejbName with error: trace.
Cause	The server was unable to create the secondary server.
Action	Please check the exception for the exact error message.

BEA-010090

Error: Failed to update secondary copy with : trace.

Description	Failed to update secondary copy with : trace.
Cause	The server was unable to update the secondary.
Action	Please check the exception for the exact error message.

BEA-010091

Error: Failure during stateful session bean replication: trace.

Description	Failure during stateful session bean replication: trace.
Cause	The container was unable to replicate the Stateful session bean.
Action	Please check the exception for the exact error message.

BEA-010092

Error: Failure while updating secondary server during replication of: jndiName. The error was: trace.

Description	Failure while updating secondary server during replication of: jndiName. The error was: trace.
Cause	The server was unable to update the secondary server.
Action	Please check the exception for the exact error message.

BEA-010094

Error: Failed to update the secondary copy of a stateful session bean from home:home.

Description	Failed to update the secondary copy of a stateful session bean from home:home.
Cause	The server was unable to update the secondary server.
Action	Please check the exception for the exact error message.

BEA-010095(retired)

Error: Skipping invalidation for component componentName (application= appName). Module had wrong type, className. 'weblogic.ejb20.deployer.EJBModule' was expected.

Description	Skipping invalidation for component componentName (application= appName). Module had wrong type, className. 'weblogic.ejb20.deployer.EJBModule' was expected.
Cause	The invalidation of the component failed. The server received the wrong Module type.
Action	Contact technical support for help.

BEA-010096

Warning: The Message-Driven EJB: ejbName is unable to connect to the JMS destination or bind to JCA resource adapter: destName. Connection failed after reconnectionCount attempts. The MDB will attempt to reconnect/rebind every jmsPollingIntervalMS seconds. This log message will repeat every errorMessageOutputTime seconds until the condition clears.

Description	The message-driven bean is having trouble connecting to the JMS destination or binding to JCA resource adapter. This message will be logged periodically until WebLogic Server can re-establish a connection.
Cause	The JMS provider or JCA resource adapter is not available, or the configuration is incorrect and WebLogic Server is not able to connect.
Action	Ensure that the JMS provider is running and is reachable using the network, or JCA resource adapter is deployed. Also ensure that the configuration information in the MDB deployment descriptor and/or annotation is correct.

BEA-010097

Info: Exception occurred during the invocation of EJB "ejbName" with primary key "primKey":

Description	Exception occurred during the invocation of EJB "ejbName" with primary key "primKey":
Cause	The bean threw a system exception.
Action	Please check the exception for the exact error message.

BEA-010098

Warning: The database type descriptorDatabaseType mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver driverDatabaseType.

Description	The database type descriptorDatabaseType mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver driverDatabaseType.
Cause	The database type descriptorDatabaseType mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver driverDatabaseType.
Action	Check the database-type tag inside weblogic-cmp-rdbms-jar.xml.

BEA-010099

Warning: WARNING(S) from EJB QL Compiler. \nwarning\n

Description	WARNING(S) from EJB QL Compiler. \nwarning\n
Cause	The compilation of EJB-QL succeeded. These are some non-fatal warnings.
Action	Please check the message for the exact warnings.

BEA-010100

Warning: This server is not part of a cluster. Hence "InMemory replication feature" for StatefulSession EJB "ejbName" will have no effect on this server.

Description	This server is not part of a cluster. Hence "InMemory replication feature" for StatefulSession EJB "ejbName" will have no effect on this server.
Cause	The bean has been deployed on a server, which is not a part of cluster. Hence the "InMemory" replication feature will be ignored.
Action	No action required.

BEA-010101

Error: A mismatch exists between the bean code and generated code.ejbName . Please rerun appc on the bean code. The error was errorMsg.

Description	A mismatch exists between the bean code and generated code.ejbName . Please rerun appc on the bean code. The error was errorMsg.
Cause	See error message body for cause.
Action	See error message body for action.

BEA-010102

Error: Error encountered while attempting to create Default DBMS Table: 'tableName'. Error Text: 'text'.

Description	Error encountered while attempting to create Default DBMS Table: 'tableName'. Error Text: 'text'.
Cause	See error message body.
Action	See error message body.

BEA-010103

Error: The Replicated Stateful Session EJB:ejbName cannot be deployed, because the In-memory Replication - EJB feature is not licensed. Please ensure that your server installation includes the proper license or contact your sales representative to obtain an In-memory Replication - EJB license.

Description	The Replicated Stateful Session EJB:ejbName cannot be deployed, because the In-memory Replication - EJB feature is not licensed. Please ensure that your server installation includes the proper license or contact your sales representative to obtain an In-memory Replication - EJB licensee.
Cause	See error message body.
Action	See error message body.

BEA-010104(retired)

Warning: Application deployment failed. You have attempted to deploy an application that uses J2EE 1.3 features while running WebLogic Server in J2EE 1.2 mode. You can configure WebLogic Server to run in J2EE 1.3 mode using the Administration Console.\n This information is based on the DTD reference of the Public ID in the ejb-jar.xml descriptor of this EJB application.

Description	Application deployment failed. You have attempted to deploy an application that uses J2EE 1.3 features while running WebLogic Server in J2EE 1.2 mode.You can configure WebLogic Server to run in J2EE 1.3 mode using the Administration Console.\nThis information is based on the DTD reference of the Public ID in the ejb-jar.xml descriptor of this EJB application.
Cause	See error message body.
Action	See error message body.

BEA-010105

Error: Unable to compile the symmetric relationship for EJB 'ejbName' that uses cmr-field 'cmrName'. A unique name must given to each role in the relationship. When editing the ejb-jar.xml deployment descriptor directly, this is done using the ejb-relationship-role-name element.

Description	Unable to compile the symmetric relationship for EJB 'ejbName' that uses cmr-field 'cmrName'. A unique name must given to each role in the relationship. When editing the ejb-jar.xml deployment descriptor directly, this is done using the ejb-relationship-role-name element.
Cause	See error message body.
Action	See error message body.

BEA-010106

Error: EJB : ejbName .Unable to initialize method info for remote or home interface. The error is logmessage.

Description	EJB : ejbName .Unable to initialize method info for remote or home interface. The error is logmessage.
Cause	See error message body.
Action	See error message body.

BEA-010107

Error: The lock request from EJB:ejbName with primary key:pk timed-out after waiting timeoutMS ms. The transaction or thread requesting the lock was:lockClient.

Description	The lock request from EJB:ejbName with primary key:pk timed-out after waiting timeoutMS ms. The transaction or thread requesting the lock was:lockClient.
Cause	See error message body.
Action	See error message body.

BEA-010108

Error: The EJB Lock Manager has received an unlock request from EJB:ejbName with primary key:pk. However, this primary key could not be found in the Lock Manager. This indicates either an EJB container bug, or the equals and hashCode methods for the primary key class:pkClassName are implemented incorrectly. Please check the equals and hashCode implementations.

Description	The EJB Lock Manager has received an unlock request from EJB:ejbName with primary key:pk. However, this primary key could not be found in the Lock Manager. This indicates either an EJB container bug, or the equals and hashCode methods for the primary key class:pkClassName are implemented incorrectly. Please check the equals and hashCode implementations.
Cause	See error message body.
Action	See error message body.

BEA-010109(retired)

Error: The findByPrimaryKeyMethod should not be defined in ejb-jar.xml. Every finder method except findByPrimaryKeyMethod should be associated with a query element in ejb-jar.xml.

Description	The findByPrimaryKeyMethod should not be defined in ejb-jar.xml. Every finder method except findByPrimaryKeyMethod should be associated with a query element in ejb-jar.xml.
Cause	See error message body.
Action	See error message body.

BEA-010110

Error: Duplicate EJB name ejbName in ejb-jar.xml.

Description	Duplicate EJB name ejbName in ejb-jar.xml.
Cause	See error message body.
Action	See error message body.

BEA-010111(retired)

Error: Errors encountered 'ejbName'.

Description	Errors encountered 'ejbName'.
Cause	See error message body.
Action	See error message body.

BEA-010112

Error: The Message Driven Bean 'ejbName' is transacted, but the provider defined in the EJB is not transacted. Provider should be transacted if onMessage method in MDB is transacted.

Description	The Message Driven Bean 'ejbName' is transacted, but the provider defined in the EJB is not transacted. Provider should be transacted if onMessage method in MDB is transacted.
Cause	See error message body.
Action	See error message body.

BEA-010113

Error: For method 'finderName' in EJB 'ejbName': caching-name can not be specified if the query return type is not 'OBJECT'.

Description	For method 'finderName' in EJB 'ejbName': caching-name can not be specified if the query return type is not 'OBJECT'.
Cause	See error message body.
Action	See error message body.

BEA-010114

Error: Dynamic queries have not been enabled for this EJB. You can enable dynamic queries by adding an enable-dynamic-queries element to your weblogic-ejb-jar.xml deployment descriptor.

Description	Dynamic queries have not been enabled for this EJB. You can enable dynamic queries by adding an enable-dynamic-queries element to your weblogic-ejb-jar.xml deployment descriptor.
Cause	See error message body.
Action	See error message body.

BEA-010115

Error: Invalid result-type-mapping for the Dynamic Query. The selected EJB: 'ejbName' does not have a mapping client view. Please update your Query with a valid result-type-mapping setting.

Description	Invalid result-type-mapping for the Dynamic Query. The selected EJB: 'ejbName' does not have a mapping client view. Please update your Query with a valid result-type-mapping setting.
Cause	See error message body.
Action	See error message body.

BEA-010116(retired)

Error: Attempted to access the collection valued cmr-field, 'cmrField', for bean, 'ejbName', outside the scope of a transaction. All access to the collection must be performed during the transaction in which the collection was initially retrieved.

Description	Attempted to access the collection valued cmr-field, 'cmrField', for bean, 'ejbName', outside the scope of a transaction. All access to the collection must be performed during the transaction in which the collection was initially retrieved.
Cause	See error message body.
Action	See error message body.

BEA-010117

Error: Attempted to access the collection valued cmr-field, 'cmrField', for bean, 'ejbName', in a transaction that is different than the transaction in which the collection was materialized. All access to the collection must be performed during the transaction in which the collection was initially retrieved.

Description	Attempted to access the collection valued cmr-field, 'cmrField', for bean, 'ejbName', in a transaction that is different than the transaction in which the collection was materialized. All access to the collection must be performed during the transaction in which the collection was initially retrieved.
Cause	See error message body.
Action	See error message body.

BEA-010118(retired)

Error: Attempted to access an iterator for the collection valued cmr-field, 'cmrField', for bean, 'ejbName', outside the scope of a transaction. All access to the iterator must be performed during the transaction in which the collection was initially retrieved.

Description	Attempted to access an iterator for the collection valued cmr-field, 'cmrField', for bean, 'ejbName', outside the scope of a transaction. All access to the iterator must be performed during the transaction in which the collection was initially retrieved.
Cause	See error message body.
Action	See error message body.

BEA-010119(retired)

Error: Attempted to access an iterator for the collection valued cmr-field, 'cmrField', of bean, 'ejbName', in a transaction that is different than the transaction in which the collection was materialized. All access to the iterator must be performed during the transaction in which the collection was initially retrieved.

Description	Attempted to access an iterator for the collection valued cmr-field, 'cmrField', of bean, 'ejbName', in a transaction that is different than the transaction in which the collection was materialized. All access to the iterator must be performed during the transaction in which the collection was initially retrieved.
Cause	See error message body.
Action	See error message body.

BEA-010120

Error: Error: The deployment descriptor 'fileName' was not found in 'jarName'. Please add this file to the JAR and try again.

Description	Error: The deployment descriptor 'fileName' was not found in 'jarName'. Please add this file to the JAR and try again.
Cause	See error message body.
Action	See error message body.

BEA-010121(retired)

Error: Problem: Could not find CMP Descriptor for EJB 'ejbName' in the CMPBeanDescriptor \n\nAction: Contact technical support for help.

Description	Problem: Could not find CMP Descriptor for EJB 'ejbName' in the CMPBeanDescriptor \n\nAction: Contact technical support for help.
Cause	See error message body.
Action	See error message body.

BEA-010122

Error: Problem: Could not find EnterpriseBeanMBean for EJB 'ejbName' in the EJBDescriptorMBean \n\nAction: Contact technical support for help.

Description	Problem: Could not find EnterpriseBeanMBean for EJB 'ejbName' in the EJBDescriptorMBean \n\nAction: Contact technical support for help.
Cause	See error message body.
Action	See error message body.

BEA-010123

Error: Problem: the EntityMBean for EJB 'ejbName' is not a version 'expectedVersion' Bean \n\nAction: Contact technical support for help.

Description	Problem: the EntityMBean for EJB 'ejbName' is not a version 'expectedVersion' Bean \n\nAction: Contact technical support for help.
Cause	See error message body.
Action	See error message body.

BEA-010124

Error: Error. Method SecurityHelper.methodName returned a NULL Principal. The CallerPrincipal Stack has been corrupted. One cause of corruption might be: A Bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.

Description	Error. Method SecurityHelper.methodName returned a NULL Principal. The CallerPrincipal Stack has been corrupted. One cause of corruption might be: A bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.
Cause	See error message body.
Action	See error message body.

BEA-010125

Error: This query has operation argument, which is an INTEGER: intVal. Specification of an INTEGER as an argument to operation is allowed only for ejbSelect queries that return a java.sql.ResultSet (in which case, we can be certain of the identity of all the DBMS columns in the SQL SELECT list).

Description	This query has operation argument, which is an INTEGER: intVal. Specification of an INTEGER as an argument to operation is allowed only for ejbSelect queries that return a java.sql.ResultSet (in which case, we can be certain of the identity of all the DBMS columns in the SQL SELECT list).
Cause	See error message body.
Action	See error message body.

BEA-010126

Error: This query has operation argument, which is an INTEGER: orderByVal. But the SELECT list of the query only specifies: selectSize elements. The operation INTEGER argument does not correspond to any argument in the SELECT list.

Description	This query has operation argument, which is an INTEGER: orderByVal. But the SELECT list of the query only specifies: selectSize elements. The operation INTEGER argument does not correspond to any argument in the SELECT list.
Cause	See error message body.
Action	See error message body.

BEA-010127

Error: Incorrect DataSource type detected. The DataSource with JNDI name 'dataSourceName', specified in the RDBMS deployment descriptor for the EJB 'ejbName' does not support global transactions. The EJB container requires a DataSource that supports global transactions to be specified for transactions to be managed correctly.

Description	Incorrect DataSource type detected. The DataSource with JNDI name 'dataSourceName', specified in the RDBMS deployment descriptor for the EJB 'ejbName' does not support global transactions. The EJB container requires a DataSource that supports global transactions to be specified for transactions to be managed correctly.
Cause	See error message body.
Action	See error message body.

BEA-010128

Error: Error during deployment of EJB 'ejbName'. The EJB references an application-level cache, 'cacheName', that is not defined in the weblogic-application.xml descriptor.

Description	Error during deployment of EJB 'ejbName'. The EJB references an application-level cache, 'cacheName', that is not defined in the weblogic-application.xml descriptor.
Cause	See error message body.
Action	See error message body.

BEA-010129

Error: Error during deployment of EJB 'ejbName'. The EJB references a 'MultiVersion' application-level cache 'cacheName', but it must use an 'Exclusive' cache instead. EJBs with a concurrency-strategy of 'Exclusive' must use an 'Exclusive' cache.

Description	Error during deployment of EJB 'ejbName'. The EJB references a 'MultiVersion' application-level cache 'cacheName', but it must use an 'Exclusive' cache instead. EJBs with a concurrency-strategy of 'Exclusive' must use an 'Exclusive' cache.
Cause	See error message body.
Action	See error message body.

BEA-010130

Error: An error occurred during deployment of EJB 'ejbName'. The EJB references an 'Exclusive' application level cache 'cacheName', but it must use a 'MultiVersion' cache instead. EJBs with a concurrency-strategy of 'Database', 'ReadOnly', or 'Optimistic' must use a 'MultiVersion' cache.

Description	An error occurred during deployment of EJB 'ejbName'. The EJB references an 'Exclusive' application level cache 'cacheName', but it must use a 'MultiVersion' cache instead. EJBs with a concurrency-strategy of 'Database', 'ReadOnly', or 'Optimistic' must use a 'MultiVersion' cache.
Cause	See error message body.
Action	See error message body.

BEA-010131(retired)

Error: Error during deployment of EJB 'ejbName'. The delay-database-insert-until tag is set to 'commit' to turn on bulk insert feature. This requires the JDBC driver to support Batch Update. The current JDBC driver does not indicate it supports Batch Update.

Description	Error during deployment of EJB 'ejbName'. The delay-database-insert-until tag is set to 'commit' to turn on bulk insert feature. This requires the JDBC driver to support Batch Update. The current JDBC driver does not indicate it supports Batch Update.
Cause	See error message body.
Action	See error message body.

BEA-010132

Error: Error during deployment of EJB 'ejbName'. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.

Description	Error during deployment of EJB 'ejbName'. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.
Cause	See error message body.
Action	See error message body.

BEA-010133

Error: Illegal attempt to assign a removed bean to a CMR field. The EJB with primary key 'pk' has been removed and cannot be assigned to this CMR field.

Description	Illegal attempt to assign a removed bean to a CMR field. The EJB with primary key 'pk' has been removed and cannot be assigned to this CMR field.
Cause	See error message body.
Action	See error message body.

BEA-010134(retired)

Error: Duplicate weblogic-rdbms-bean 'beanName' found in RDBMS CMP descriptor 'fileName'.

Description	Duplicate weblogic-rdbms-bean 'beanName' found in RDBMS CMP descriptor 'fileName'.
Cause	See error message body.
Action	See error message body.

BEA-010135(retired)

Error: Duplicate weblogic-rdbms-relation 'relationName' found in RDBMS CMP descriptor 'fileName'.

Description	Duplicate weblogic-rdbms-relation 'relationName' found in RDBMS CMP descriptor 'fileName'.
Cause	See error message body.
Action	See error message body.

BEA-010136

Error: Param must be an integer.

Description	Param must be an integer.
Cause	See error message body.
Action	See error message body.

BEA-010137

Error: Param must be an positive integer.

Description	Param must be an positive integer.
Cause	See error message body.
Action	See error message body.

BEA-010138

Error: Invalid field-group name. No field-group with the name 'groupName' was declared for this EJB in the RDBMS deployment descriptor.

Description	Invalid field-group name. No field-group with the name 'groupName' was declared for this EJB in the RDBMS deployment descriptor.
Cause	See error message body.
Action	See error message body.

BEA-010139

Error: Bean with primary key 'pk' already exists.

Description	Bean with primary key 'pk' already exists.
Cause	See error message body.
Action	See error message body.

BEA-010140

Error: Bean with primary key: 'pk' not found.

Description	Bean with primary key: 'pk' not found.
Cause	See error message body.
Action	See error message body.

BEA-010141

Error: Creation of Many-To-Many relationship for primary key: 'pk1' and 'pk2' effected 'effected' rows in 'joinTableName', instead of just 1.

Description	Creation of Many-To-Many relationship for primary key: 'pk1' and 'pk2' effected 'effected' rows in 'joinTableName', instead of just 1.
Cause	See error message body.
Action	See error message body.

BEA-010142

Error: Instance of EJB 'relatedEJBName' with primary key 'pk' does not exist.

Description	Instance of EJB 'relatedEJBName' with primary key 'pk' does not exist.
Cause	See error message body.
Action	See error message body.

BEA-010143

Error: Optimistic concurrency violation. Instance of bean 'ejbName' with primary key 'pk' was changed by another transaction.

Description	Optimistic concurrency violation. Instance of bean 'ejbName' with primary key 'pk' was changed by another transaction.
Cause	See error message body.
Action	See error message body.

BEA-010144

Error: The setXXX method for a primary key field may only be called during ejbCreate.

Description	The setXXX method for a primary key field may only be called during ejbCreate.
Cause	See error message body.
Action	See error message body.

BEA-010145

Error: When a cmp-field and a cmr-field (relationship) are mapped to the same column, the setXXX method for the cmp-field may not be called. The cmp-field is read-only.

Description	When a cmp-field and a cmr-field (relationship) are mapped to the same column, the setXXX method for the cmp-field may not be called. The cmp-field is read-only.
Cause	See error message body.
Action	See error message body.

BEA-010146

Error: The setXXX method for a cmr-field that is mapped to a primary key may not be called. The cmr-field is read-only.

Description	The setXXX method for a cmr-field that is mapped to a primary key may not be called. The cmr-field is read-only.
Cause	See error message body.
Action	See error message body.

BEA-010147

Error: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.

Description	The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.
Cause	See error message body.
Action	See error message body.

BEA-010148

Error: In EJB 'ejbName', the primary key field 'pk' was not set during ejbCreate. All primary key fields must be initialized during ejbCreate.

Description	In EJB 'ejbName', the primary key field 'pk' was not set during ejbCreate. All primary key fields must be initialized during ejbCreate.
Cause	See error message body.
Action	See error message body.

BEA-010149

Error: According to the EJB 2.0 specification, a value of ''null'' may not be assigned to a collection valued cmr-field.

Description	According to the EJB 2.0 specification, a value of ''null'' may not be assigned to a collection valued cmr-field.
Cause	See error message body.
Action	See error message body.

BEA-010150(retired)

Error: Field 'pkFieldName' not found in class 'pkClass'.

Description	Field 'pkFieldName' not found in class 'pkClass'.
Cause	See error message body.
Action	See error message body.

BEA-010151(retired)

Error: An attempt was made to access a collection valued cmr-field outside the scope of a transaction.

Description	An attempt was made to access a collection valued cmr-field outside the scope of a transaction.
Cause	See error message body.
Action	See error message body.

BEA-010152

Error: Illegal value for concurrency-strategy. Value was 'val', but must be one of 'ReadOnly', 'Exclusive','Database', or 'Optimistic'.

Description	Illegal value for concurrency-strategy. Value was 'val', but must be one of 'ReadOnly', 'Exclusive','Database', or 'Optimistic'.
Cause	See error message body.
Action	See error message body.

BEA-010153

Error: Only instances of beans with a remote client view can invoke getEJBObject().

Description	Only instances of beans with a remote client view can invoke getEJBObject().
Cause	See error message body.
Action	See error message body.

BEA-010154

Error: Only instances of beans with a local client view can invoke getEJBLocalObject().

Description	Only instances of beans with a local client view can invoke getEJBLocalObject().
Cause	See error message body.
Action	See error message body.

BEA-010155

Error: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().

Description	Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().
Cause	See error message body.
Action	See error message body.

BEA-010156

Error: Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction.

Description	Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction.
Cause	See error message body.
Action	See error message body.

BEA-010157

Error: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().

Description	Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().
Cause	See error message body.
Action	See error message body.

BEA-010158

Error: Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction.

Description	Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction.
Cause	See error message body.
Action	See error message body.

BEA-010159

Error: Error: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, ejbName, was deployed without a JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Description	Error: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, ejbName, was deployed without a JNDI name specified. To specify a JNDI name for this EJB, please add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Cause	See error message body.
Action	See error message body.

BEA-010160

Error: Security Violation: User: 'userName' has insufficient permission to access EJB: EJBResource.

Description	Security Violation: User: 'userName' has insufficient permission to access EJB: EJBResource.
Cause	See error message body.
Action	See error message body.

BEA-010161

Error: The handle was null.

Description	The handle was null.
Cause	See error message body.
Action	See error message body.

BEA-010162

Error: EJBObject from handle was null.

Description	EJBObject from handle was null.
Cause	See error message body.
Action	See error message body.

BEA-010163

Error: handle.getEJBObject().getEJBHome() was null.

Description	handle.getEJBObject().getEJBHome() was null.
Cause	See error message body.
Action	See error message body.

BEA-010164

Error: The EJBObject represented by this handle is not from this EJBHome.

Description	The EJBObject represented by this handle is not from this EJBHome.
Cause	See error message body.
Action	See error message body.

BEA-010165

Error: Illegal attempt to invoke EJBMetaData.getPrimaryKeyClass() on a session bean.

Description	Illegal attempt to invoke EJBMetaData.getPrimaryKeyClass() on a session bean.
Cause	See error message body.
Action	See error message body.

BEA-010166

Error: Error occurred while starting transaction: reason.

Description	Error occurred while starting transaction: reason.
Cause	See error message body.
Action	See error message body.

BEA-010167

Error: Message-driven beans are not allowed to call methodName.

Description	Message-driven beans are not allowed to call methodName.
Cause	See error message body.
Action	See error message body.

BEA-010168

Error: Method 'methodName' has been declared in an assembly-descriptor exclude-list and cannot be executed.

Description	Method 'methodName' has been declared in an assembly-descriptor exclude-list and cannot be executed.
Cause	See error message body.
Action	See error message body.

BEA-010169

Error: Security violation: insufficient permission to access method 'methodName'.

Description	Security violation: insufficient permission to access method 'methodName'.
Cause	See error message body.
Action	See error message body.

BEA-010170(retired)

Error: No mapping from EJB Security Role to WLS Principal Name reason.

Description	No mapping from EJB Security Role to WLS Principal Name reason.
Cause	See error message body.
Action	See error message body.

BEA-010171

Error: Illegal attempt to call EJBObject.getPrimaryKey() on a session bean.

Description	Illegal attempt to call EJBObject.getPrimaryKey() on a session bean.
Cause	see message body
Action	see message body

BEA-010172

Error: Cannot remove stateless session beans using EJBHome.remove(Object primaryKey).

Description	Cannot remove stateless session beans using EJBHome.remove(Object primaryKey).
Cause	See error message body.
Action	See error message body.

BEA-010173

Error: env-entry for type java.lang.Character had length = 0.

Description	env-entry for type java.lang.Character had length = 0.
Cause	See error message body.
Action	See error message body.

BEA-010174

Error: The resource-ref 'resourceRefName' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.

Description	The resource-ref 'resourceRefName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
Cause	See error message body.
Action	See error message body.

BEA-010175(retired)

Error: Could not locate resource-ref 'resourceRefName' in application environment and no resource-description given to map res-ref-name to global environment.Yahoo.

Description	Could not locate resource-ref 'resourceRefName' in application environment and no resource-description given to map res-ref-name to global environment.Yahoo.
Cause	See error message body.
Action	See error message body.

BEA-010176

Error: The resource-env-ref 'resourceEnvRefName' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.

Description	The resource-env-ref 'resourceEnvRefName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor.
Cause	See error message body.
Action	See error message body.

BEA-010177

Error: Could not create a new JMS ConnectionFactory for the application: stackTrace.

Description	Could not create a new JMS ConnectionFactory for the application: stackTrace.
Cause	See error message body.
Action	See error message body.

BEA-010178(retired)

Error: Could not resolve ejbLink: 'ejbLing'. The specified EJB could not be found in this application.

Description	Could not resolve ejbLink: 'ejbLing'.
Cause	An incorrect ejb-link was specified in the ejb-jar.xml file.
Action	Verify that your ejb-link value is correct.

BEA-010179

Error: Illegal attempt to call EJBLocalObject.getPrimaryKey() on a session bean.

Description	Illegal attempt to call EJBLocalObject.getPrimaryKey() on a session bean.
Cause	See error message body.
Action	See error message body.

BEA-010180

Error: Illegal Reentrant call to 'ejbName' with primary key: 'pk'.

Description	Illegal Reentrant call to 'ejbName' with primary key: 'pk'.
Cause	See error message body.
Action	See error message body.

BEA-010181

Error: The findByPrimaryKey method from home: 'ejbName' was passed: 'pk' but it returned null.

Description	The findByPrimaryKey method from home: 'ejbName' was passed: 'pk' but it returned null.
Cause	See error message body.
Action	See error message body.

BEA-010182

Error: The 'finderName' method from home: 'ejbName' returned null.

Description	The 'finderName' method from home: 'ejbName' returned null.
Cause	See error message body.
Action	See error message body.

BEA-010183

Warning: javax.ejb.EJBContext.getEnvironment is deprecated in EJB 1.1. EJB 1.1 compliant containers are not required to implement this method. Use java:comp/env instead.

Description	javax.ejb.EJBContext.getEnvironment is deprecated in EJB 1.1. EJB 1.1 compliant containers are not required to implement this method. Use java:comp/env instead.
Cause	See error message body.
Action	See error message body.

BEA-010184

Error: Unrecognized method name format for 'signature': Expected NAME or NAME() or NAME(arg1,arg2,...).

Description	Unrecognized method name format for 'signature': Expected NAME or NAME() or NAME(arg1,arg2,...).
Cause	See error message body.
Action	See error message body.

BEA-010185

Error: Bean with primary key: 'pk' not created.

Description	Bean with primary key: 'pk' not created.
Cause	See error message body.
Action	See error message body.

BEA-010186

Error: Bean not found in 'finderMethodName'.

Description	Bean not found in 'finderMethodName'.
Cause	See error message body.
Action	See error message body.

BEA-010188

Error: Error encountered while attempting to drop Default DBMS Table: 'tableName'. Error Text: 'text'.

Description	Error encountered while attempting to drop Default DBMS Table: 'tableName'. Error Text: 'text'.
Cause	See error message body.
Action	See error message body.

BEA-010189

Error: Error encountered while attempting to alter Default DBMS Table: 'tableName'. Error Text: 'text'.

Description	Error encountered while attempting to alter Default DBMS Table: 'tableName'. Error Text: 'text'.
Cause	See error message body.
Action	See error message body.

BEA-010190

Error: \nProblem, cmp-field 'cmpField' is mapped to a Blob or Clob column. The ORDER BY clause may not specify cmp-fields that map to Blob or Clob columns. \n\nAction, remove the cmp-field 'cmpField' from the ORDER BY clause.

Description	\nProblem, cmp-field 'cmpField' is mapped to a Blob or Clob column. The ORDER BY clause may not specify cmp-fields that map to Blob or Clob columns. \n\nAction, remove the cmp-field 'cmpField' from the ORDER BY clause.
Cause	see message body
Action	see message body

BEA-010191

Error: The alter table option is not supported in dbName. Please use the DropAndCreate option.

Description	The alter table option is not supported in dbName. Please use the DropAndCreate option.
Cause	See error message body.
Action	See error message body.

BEA-010193

Error: Illegal call to EJBContext method. The bean is in "beanState" state. It cannot perform actionsDescription action(s). Refer to the EJB specification for more details.

Description	Illegal call to EJBContext method. The bean is in "beanState" state. It cannot perform actionsDescription action(s). Refer to the EJB specification for more details.
Cause	See error message body.
Action	See error message body.

BEA-010194

Error: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().

Description	Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().
Cause	See error message body.
Action	See error message body.

BEA-010195

Error: Security violation: User 'user' has insufficient permission to access method 'methodName'.

Description	Security violation: User 'user' has insufficient permission to access method 'methodName'.
Cause	See error message body.
Action	See error message body.

BEA-010196(retired)

Error: 'exception' Linked exception = 'linked'

Description	'exception' Linked exception = 'linked'
Cause	See error message body.
Action	See error message body.

BEA-010197

Warning: The entity bean ejbName uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.

Description	The entity bean ejbName uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.
Cause	See error message body.
Action	See error message body.

BEA-010198

Warning: An Exception occurred while uninitializing the EJB module moduleName:

Description	After a previous Exception was thrown while performing a deployment task, this secondary Exception was thrown while uninitializing the EJB module. This secondary Exception may or may not be of importance to the user. Note that this secondary Exception may cause problems for future deployment tasks involving this EJB module. If this is the case, try removing the application and retry the deployment task.
Cause	Please check the exception for the exact cause.
Action	Please check the exception for the exact error message.

BEA-010199

Warning: EJB ejbName with run as role runAsRole has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name principal from the security-role-assignment list for role runAsRole to be the run as principal name.

Description	See error message body.
Cause	See error message body.
Action	See error message body.

BEA-010200(retired)

Warning: The EJB Module 'moduleName' has a class 'className' that contains a member. To update this class or any of its superclasses, you must redeploy the entire EJB Module. You cannot update these classes using the dynamic EJB impl class update feature.

Description	The EJB class mentioned in the error message contains a public static Field or Method or a non-private inner class. To ensure backward compatibility, we cannot load these classes in a child ClassLoader of the application ClassLoader. Because of this, the dynamic EJB impl class update feature is disabled.
Cause	See detail.
Action	The user has two choices. They can do nothing which will mean they can never update the EJB impl class dynamically (unless they redeploy the entire Application or EJB Module. Alternatively, the user can modify their bean class as to not contain any public static fields, methods or non-private inner classes.

BEA-010201

Error: The message-driven bean, 'ejbName', encountered an error while recovering a JMS session. This is a secondary error. The original error occurred while the message-driven bean was processing a message. The recover action was taken in an attempt to recover from the original error, which will be logged separately.

Description	The message-driven bean encountered an error while recovering a JMS session. This action takes place after an error occurs inside the message-driven bean itself, which causes the server to try to return the current message back to the queue or topic.
Cause	The message-driven bean may have thrown an exception, or there may be a problem with the JMS provider.
Action	Check that the JMS provider is running and accessible through the network. Also, check that the message-driven bean onMessage method does not throw any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.

BEA-010202

Warning: Call-by-reference is not enabled for the EJB 'ejbName'. The server will have better performance if it is enabled. To enable call-by-reference, set the enable-call-by-reference element to True in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Description	Call-by-reference is not enabled for the specified EJB so call-by-value will always be used for method invocations on the remote interfaces. Although this will not cause any errors in your application, it may hurt performance. In general, we recommend enabling call-by-reference via the enable-call-by-reference element in your weblogic-ejb-jar.xml deployment descriptor or annotation. Note, however, that your application code must take into account that call-by-reference is used or unexpected errors may occur.
Cause	Call-by-reference is not enabled.
Action	If appropriate, enable call-by-reference in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for the EJB.

BEA-010203(retired)

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.

BEA-010204

Info: The EJB component, moduleName will be rolled back and redeployed to update the class 'className'. This class is not a bean implementation class. Only bean implementation classes can be updated without redeploying the entire module, and only when enable-bean-class-redeploy is set to 'True' in weblogic-ejb.jar.xml.

Description	The EJB module received a command to update the specified class. Since the class is not a bean implementation class, the only way it could be updated is to rollback and redeploy the entire EJB module. This must be done to reset the ClassLoader for the specified class.
Cause	A command was issued to update the specified class.
Action	No action is necessary, this is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.

BEA-010205

Info: The EJB module, moduleName will be rolled back and redeployed to update the class 'className'. Bean implementation classes, such as this, can be updated without redeploying the entire EJB module. However, this can only be done if enable-bean-class-redeploy is set to 'True' in weblogic-ejb.jar.xml or corresponding annotation. If this is the behavior you want, please set this value to 'True' and redeploy.

Description	The EJB module received a command to update the specified class. Since the class was not loaded in a separate ClassLoader, the only way it could be updated is to rollback and redeploy the entire EJB module. To ensure this class is loaded in a separate ClassLoader, and can therefore be redeployed without rolling back the entire EJB module, set the enable-bean-class-redeploy value to true in the weblogic-ejb-jar.xml descriptor for this EJB.
Cause	A command was issued to update the specified class.
Action	No action is necessary, this is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.

BEA-010206

Info: The EJB module, moduleName will be rolled back and redeployed to update the class 'className'. This bean implementation class could not be updated without redeploying the entire EJB module because it was changed incompatibly. Incompatible changes are any changes that cause the EJB compiler to be run. This includes modifying a public variable name or a public method signature.

Description	The EJB module received a command to update the specified class. Since the class was changed incompatibly, the only way it could be updated is to rollback and redeploy the entire EJB module. To ensure this a class is not changed incompatibly, ensure you do not change public variable names or public method signatures after the EJB compiler was run.
Cause	A command was issued to update the specified class.
Action	No action is necessary, this is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.

BEA-010207

Info: License validation not passed for ejbVersion.

Description

License validation not passed for ejbVersion.

BEA-010208

Info: ddl-file "ddlFileName" created.

Description

ddl-file "ddlFileName" created.

BEA-010209

Info: ddl-file "ddlFileName" could not be deleted.

Description	ddl-file "ddlFileName" could not be deleted.
Action	Please check the file permissions.

BEA-010210

Info: Unable to write to ddl-file "ddlFileName"

Description

Unable to write to ddl-file "ddlFileName"

BEA-010211

Info: Unable to alter the table as the primary key has changed.

Description	Unable to alter the table as the primary key has changed.
Action	Please use the DropAndCreate option to create the table.

BEA-010212

Warning: The EJB 'ejbName' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of default will be used for the following methods: methods

Description	The specified EJB uses container managed transactions but an explicit transaction attribute was not specified for some methods in the ejb-jar.xml deployment descriptor or corresponding annotation. These methods will use a default transaction attribute. Note that the default transaction attribute will not result in a new transaction being started.
Cause	The ejb-jar.xml deployment descriptor or corresponding annotation does not contain transaction attribute settings for the specified EJB methods.
Action	Please assign transaction attributes for all methods of your EJB.

BEA-010213

Info: Message-Driven EJB: ejbName's transaction was rolled back. The transaction details are: errorMessage.

Description	Message-Driven EJB: ejbName's transaction was rolled back. The transaction details are: errorMessage.
Cause	The transaction was rolled back by the mdb container.

BEA-010214

Error: Error starting MDB t

Description	The attempt to start processing message driven beans failed during server startup.
Cause	Please inspect the log file for indications of the root cause of the failure.
Action	Please inspect the log file for indications of the root cause of the failure.

BEA-010215

Info: The durable subscription store with jms-client-id equal to 'jmsClientID' is deleted when MDB 'ejbName' is removed from the server.

Description	The durable subscription store is deleted when MDB is removed from the server and its durable-subscription-deletion set to true.
Cause	The durable subscription store is deleted when MDB is removed from the server and its durable-subscription-deletion set to true.
Action	Info message. No action needed.

BEA-010216

Warning: The Message-Driven EJB: ejbName is throwing exception when processing the messages. Delivery failed after deliveryFailureCount attempts. The EJB container will suspend the message delivery for errorMessageOutputTime seconds before retry.

Description	The message-driven bean is throwing exception when processing the messages. The EJB container will suspend the message delivery for a few seconds before retry.
Cause	The message-driven bean is throwing exception.
Action	Check the message delivery methods, resolve exception condition.

BEA-010220(retired)

Warning: The jms destination 'jmsDisDestName' is a distributed destination and it has no physical destination(s) on the current weblogic server. As per distributed destination co-location rules, no pool was created for the MDB 'ejbName' on this weblogic server. Hence the MDB 'ejbName' cannot receive any messages on this server.

Description	The jms destination 'jmsDisDestName' is a distributed destination and it has no physical destination(s) on the current weblogic server. As per distributed destination co-location rules, no pool was created for the MDB 'ejbName' on this weblogic server. Hence the MDB 'ejbName' cannot receive any messages on this server.
Cause	See message body.
Action	Please refer to the MDB documentation for distributed destination co-location rules.

BEA-010221

Warning: The Message-Driven EJB: ejbName is unable to bind to the JCA resource adapter: destName. The Error was:\nerrorMsg

Description	The Message-Driven EJB is unable to bind to the JCA resource adapter. The EJB container will automatically attempt to re-bind with JCA resource adapter.
Cause	The JCA resource adapter is not deployed, or the configuration information in the MDB deployment descriptor or corresponding annotation is incorrect.
Action	Check that the JCA resource adapter is deployed and the configuration information in the MDB deployment descriptor or corresponding annotation is correct.

BEA-010222

Error: The aggregate query 'finderMethodName' has a primitive return type but the query returned null because there were no values to apply the aggregate function to.

Description	The EJB query returns a primitive and no values were found by the query to apply the aggregate function to. In such situations, the EJB specification requires an EJB Container to throw an ObjectNotFoundException to signal the fact the query result was null.
Cause	See error message body.
Action	See error message body.

BEA-010223

Info: EJB Deployed Message Driven Bean: beanFile

Description

EJB Deployed Message Driven Bean: beanFile

BEA-010224

Info: The EJB Timer: timerInfo has failed to successfully timeout in attempts consecutive attempts. The container will delay the timeout for delay milliseconds as configured for the timer.

Description	When this EJB Timer was created, a retry delay was specified. The ejbTimeout for this Timer has failed due to either an Exception being thrown or a rolled back transaction. The timer expiration will be retried, but the configured delay is now in effect.
Cause	A failed ejbTimeout.
Action	Its possible that no action needs to be taken. However, it may be good to investigate why the original ejbTimeout failed.

BEA-010225

Info: The EJB Timer: timerInfo has failed to successfully timeout in attempts consecutive attempts. Since no retry delay was configured for this timer, the container will automatically delay the timeout for delay seconds.

Description	When this EJB Timer was created, a retry delay was not specified. The ejbTimeout for this Timer has consecutively failed due to either an Exception being thrown or a rolled back transaction. The timer expiration will be retried, but an automatic delay is now in effect. The automatic delay is to prevent this timer from tying up a thread while the timer is continually retried.
Cause	A failed ejbTimeout.
Action	Its possible that no action needs to be taken. However, it may be good to investigate why the ejbTimeout has consecutively failed.

BEA-010226

Error: Error executing clustered EJB timer for EJB 'ejbName' of Module 'moduleName' of application 'appName'. While executing, the timer was unable to find a necessary internal resource required to execute. The most likely cause of this issue is that the EJB is no longer configured to use the clustered EJB timer service but timers still exist in the database.

Description	During the execution of a clustered EJB timer, the timer was unable to find the necessary resources to execute. As a result, the timer has failed to execute as scheduled.
Cause	The most likely cause of this error is that the EJB associated with this Timer is no longer configured to use the clustered EJB timer service.
Action	If the EJB in question is no longer configured to use EJB timers, the timers associated with it should be removed from the database. This can be achieved by reenabling clustered EJB timers for the EJB and then undeploying the EJB. This will cause any timers associated with the EJB to be removed from the database.

BEA-010227

Info: EJB Exception occurred during invocation from home or business: ejbHome threw exception: throwable

Description

EJB Exception occurred during invocation from home or business: ejbHome threw exception: throwable

BEA-010228

Error: Failed to update the secondary copy of a stateful session bean business:home.

Description	Failed to update the secondary copy of a stateful session bean business:home.
Cause	The server was unable to update the secondary server.
Action	Please check the exception for the exact error message.

BEA-010229

Error: EJB : ejbName .Unable to initialize method info for remote ,home , message listener or webservice endpoint interface. The error is logmessage.

Description	EJB : ejbName .Unable to initialize method info for remote ,home , message listener or webservive endpoint interface. The error is logmessage.
Cause	See error message body.
Action	See error message body.

BEA-011001

Error: Installation file fileName does not exist. Could not initialize EJB container-managed persistence.

Description	Installation file fileName does not exist. Could not initialize EJB container-managed persistence.
Cause	See error message body.
Action	See error message body.

BEA-011002

Error: Installation file fileName is not readable. Could not initialize EJB container-managed persistence.

Description	Installation file fileName is not readable. Could not initialize EJB container-managed persistence.
Cause	See error message body.
Action	See error message body.

BEA-011003

Error: Installation file fileName could not be opened. Could not initialize EJB container-managed persistence.

Description	Installation file fileName could not be opened. Could not initialize EJB container-managed persistence.
Cause	See error message body.
Action	See error message body.

BEA-011004

Error: Error occurred while loading persistence resource resourceName. Make sure that the persistence type is in your classpath.

Description	Error occurred while loading persistence resource resourceName. Make sure that the persistence type is in your classpath.
Cause	See error message body.
Action	See error message body.

BEA-011005

Error: Could not find an XML processor for persistence vendor descriptor resourceName. The document probably references an unknown DTD. Contact your EJB CMP persistence provider.

Description	Could not find an XML processor for persistence vendor descriptor resourceName. The document probably references an unknown DTD. Contact your EJB CMP persistence provider.
Cause	See error message body.
Action	See error message body.

BEA-011006

Error: Unable to bind a cluster-aware stateless session EJBObject to the name: name. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.

Description	Unable to bind a cluster-aware stateless session EJBObject to the name: name. Please ensure that the jndi-name in the weblogic-ejb-jar.xml is correct.
Cause	See error message body.
Action	See error message body.

BEA-011007

Error: Unable to create EJB Persistence Manager.

Description	Unable to create EJB Persistence Manager.
Cause	See error message body.
Action	See error message body.

BEA-011008

Error: Unable to bind EJB Home Interface to the JNDI name: jndiName.

Description	Unable to bind EJB Home Interface to the JNDI name: jndiName.
Cause	See error message body.
Action	See error message body.

BEA-011009

Error: Unable to create a JNDI InitialContext to lookup the JMS destination.

Description	Unable to create a JNDI InitialContext to lookup the JMS destination.
Cause	See error message body.
Action	See error message body.

BEA-011010

Error: The JMS destination with the JNDI name: name could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.

Description	The JMS destination with the JNDI name: name could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS destination has been deployed.
Cause	See error message body.
Action	See error message body.

BEA-011011

Error: The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: name. However, the object with the JNDI name: name is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).

Description	The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: name. However, the object with the JNDI name: name is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).
Cause	See error message body.
Action	See error message body.

BEA-011012

Error: The JMS connection factory with the JNDI name: name could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS connection factory has been deployed.

Description	The JMS connection factory with the JNDI name: name could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS connection factory has been deployed.
Cause	See error message body.
Action	See error message body.

BEA-011013

Error: The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: name. However, the object with the JNDI name: name is not a JMS connection factory.

Description	The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: name. However, the object with the JNDI name: name is not a JMS connection factory.
Cause	See error message body.
Action	See error message body.

BEA-011014

Error: The Message-Driven EJB failed while creating a JMS Connection. The error was:\nmsg.

Description	The Message-Driven EJB failed while creating a JMS Connection. The error was:\nmsg.
Cause	See error message body.
Action	See error message body.

BEA-011015

Error: The Message-Driven EJB did not specify a JNDI name for its destination. Please make sure you have a message-driven-descriptor element in your weblogic-ejb-jar.xml or corresponding annotation.

Description	The Message-Driven EJB did not specify a JNDI name for its destination. Please make sure you have a message-driven-descriptor element in your weblogic-ejb-jar.xml.
Cause	See error message body.
Action	See error message body.

BEA-011016

Error: The persistence layer of the Entity EJB failed to deploy.

Description	The persistence layer of the Entity EJB failed to deploy.
Cause	See the error message body.
Action	See the error message body.

BEA-011017

Error: Error while reading 'fileName'. The error was:\n errorMsg.

Description	Error while reading 'fileName'. The error was:\n errorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011018

Error: The file fileName, specified in a type-storage element of your weblogic-ejb-jar.xml descriptor, does not exist in the JAR file.

Description	The file fileName, specified in a type-storage element of your weblogic-ejb-jar.xml descriptor, does not exist in the JAR file.
Cause	See the error message body.
Action	See the error message body.

BEA-011019

Error: While reading fileName, the persistence layer of the Entity EJB failed to deploy. The error was:\n Error in descriptor line lineNumber: errorMsg.

Description	While reading fileName, the persistence layer of the Entity EJB failed to deploy. The error was:\n Error in descriptor line lineNumber: errorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011020

Error: The database table: tableName does not contain the columns: missingColumns. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.

Description	The database table: tableName does not contain the columns: missingColumns. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.
Cause	See the error message body.
Action	See the error message body.

BEA-011021(retired)

Error: The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map. The error was:\nerrorMsg.

Description	The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map. The error was:\nerrorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011022

Error: Unable to create temporary directory: path. Please ensure that the server has write permission for this directory.

Description	Unable to create temporary directory: path. Please ensure that the server has write permission for this directory.
Cause	See the error message body.
Action	See the error message body.

BEA-011023

Error: An error occurred while reading the deployment descriptor. The error was:\n errorMsg.

Description	An error occurred while reading the deployment descriptor. The error was:\n errorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011024

Error: The XML parser encountered an error in your deployment descriptor. Please ensure that your deployment descriptor corresponds to the format in the DTD. The error was:\n errorMsg.

Description	The XML parser encountered an error in your deployment descriptor. Please ensure that your deployment descriptor corresponds to the format in the DTD. The error was:\n errorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011025

Error: The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:\nerrorMsg.

Description	The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:\nerrorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011026

Error: The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.

Description	The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
Cause	See the error message body.
Action	See the error message body.

BEA-011027

Error: The EJB container was unable to load the jts driver: weblogic.jdbc.jts.Driver. Please ensure that your classpath is set appropriately.

Description	The EJB container was unable to load the jts driver: weblogic.jdbc.jts.Driver. Please ensure that your classpath is set appropriately.
Cause	See the error message body.
Action	See the error message body.

BEA-011028

Error: The DataSource with the JNDI name: dsName could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.

Description	The DataSource with the JNDI name: dsName could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
Cause	See the error message body.
Action	See the error message body.

BEA-011029

Error: Could not get a connection from the DataSource with the JNDI name: dsName.

Description	Could not get a connection from the DataSource with the JNDI name: dsName.
Cause	See the error message body.
Action	See the error message body.

BEA-011030

Error: Could not get a Connection from: name.

Description	Could not get a Connection from: name.
Cause	See the error message body.
Action	See the error message body.

BEA-011031(retired)

Error: The Entity EJB requires the table: tableName to be accessible. Please ensure that this table exists and is accessible.

Description	The Entity EJB requires the table: tableName to be accessible. Please ensure that this table exists and is accessible.
Cause	See the error message body.
Action	See the error message body.

BEA-011032

Error: The container was unable to determine the java.sql.Types of database columns.

Description	The container was unable to determine the java.sql.Types of database columns for an unknown reason.Please try redeploying your bean.
Cause	See the error message body.
Action	See the error message body.

BEA-011033

Error: Automatic Key Generation Error: could not get Generated PK Value. No RESULT from Query: genWLKeyGeneratorQuery.

Description	Automatic Key Generation Error: could not get Generated PK Value. No RESULT from Query: genWLKeyGeneratorQuery.
Cause	See the error message body.
Action	See the error message body.

BEA-011034(retired)

Error: Automatic Key Generation: Error encountered while attempting setup and verify NAMED SEQUENCE TABLE tableName.

Description	Automatic Key Generation: Error encountered while attempting setup and verify NAMED SEQUENCE TABLE tableName.
Cause	See the error message body.
Action	See the error message body.

BEA-011035(retired)

Error: Automatic Key Generation Error: Named Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.

Description	Automatic Key Generation Error: Named Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.
Cause	See the error message body.
Action	See the error message body.

BEA-011036(retired)

Error: Automatic Key Generation Error: Error while attempting to BEGIN a new transaction prior to FETCH of next key from Named Sequence Table: sqlException.

Description	Automatic Key Generation Error: Error while attempting to BEGIN a new transaction prior to FETCH of next key from Named Sequence Table: sqlException.
Cause	See the error message body.
Action	See the error message body.

BEA-011037(retired)

Error: Automatic Key Generation Error: attempted to UPDATE or QUERY NAMED SEQUENCE TABLE tableName, but encountered SQLException sqlException.

Description	Automatic Key Generation Error: attempted to UPDATE or QUERY NAMED SEQUENCE TABLE tableName, but encountered SQLException sqlException.
Cause	See the error message body.
Action	See the error message body.

BEA-011038(retired)

Error: Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to NAMED SEQUENCE TABLE tableName, but encountered Exception exception.

Description	Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to NAMED SEQUENCE TABLE tableName, but encountered Exception exception.
Cause	See the error message body.
Action	See the error message body.

BEA-011039(retired)

Error: Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.

Description	Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.
Cause	See the error message body.
Action	See the error message body.

BEA-011040(retired)

Error: Automatic Key Generation Error: EJB: ejbName. Specifying Automatic Key Generation for Beans with Compound Keys is not allowed. This Bean has Primary Key Fields: keyList.

Description	Automatic Key Generation Error: EJB: ejbName. Specifying Automatic Key Generation for Beans with Compound Keys is not allowed. This Bean has Primary Key Fields: keyList.
Cause	See the error message body.
Action	See the error message body.

BEA-011041(retired)

Error: Automatic Key Generation Error: EJB: ejbName. Specifying Automatic Key Generation, the PK field type must be java.lang.Integer or java.lang.Long. This bean has Primary Key Fields Class: className.

Description	Automatic Key Generation Error: EJB: ejbName. Specifying Automatic Key Generation, the PK field type must be java.lang.Integer or java.lang.Long. This bean has Primary Key Fields Class: className.
Cause	See the error message body.
Action	See the error message body.

BEA-011042

Error: Stateful Session EJBs cannot be used concurrently. If a stateful session EJB instance is in the middle of a method call and another call is attempted on this instance, a java.rmi.RemoteException is thrown. You may also consider setting the option in your weblogic-ejb-jar.xml. When this tag is set, the concurrent call waits for the first method call to complete.

Description	Stateful Session EJBs cannot be used concurrently. If a stateful session EJB instance is in the middle of a method call and another call is attempted on this instance, a java.rmi.RemoteException is thrown. You may also consider setting the option in your weblogic-ejb-jar.xml. When this tag is set, the concurrent call waits for the first method call to complete.
Cause	See the error message body.
Action	See the error message body.

BEA-011043

Error: ReadOnlyHome.invalidate() was called with a null parameter. You must either pass a primary key or a collection of primary keys. See the weblogic.ejb.ReadOnlyHome interface for more information.

Description	ReadOnlyHome.invalidate() was called with a null parameter. You must either pass a primary key or a collection of primary keys. See the weblogic.ejb.ReadOnlyHome interface for more information.
Cause	See the error message body.
Action	See the error message body.

BEA-011044

Error: ReadOnlyHome.invalidate from EJB:ejbName failed while attempting to send a multicast cache invalidation message.

Description	ReadOnlyHome.invalidate from EJB:ejbName failed while attempting to send a multicast cache invalidation message.
Cause	See the error message body.
Action	See the error message body.

BEA-011045(retired)

Error: The pool poolName could not be found. Please make sure it is declared in your config.xml.

Description	The pool poolName could not be found. Please make sure it is declared in your config.xml.
Cause	See the error message body.
Action	See the error message body.

BEA-011046

Error: Unable to create EJBRuntimeMBean.

Description	Unable to create EJBRuntimeMBean.
Cause	See the error message body.
Action	See the error message body.

BEA-011047

Warning: Warning: In 'ejb-jar.xml' or annotation, EJB 'ejbName' has container-transactions set when the EJB has a transaction-type of 'Bean'. The container-transaction settings will be ignored.

Description	Warning: In 'ejb-jar.xml', EJB 'ejbName' has container-transactions set when the EJB has a transaction-type of 'Bean'. The container-transaction settings will be ignored.
Cause	See the error message body.
Action	See the error message body.

BEA-011048

Error: Finder-expressions are no longer supported.

Description	Finder-expressions are no longer supported.
Cause	See the error message body.
Action	See the error message body.

BEA-011049

Error: Unable to find bean 'ejbName' in RDBMS CMP deployment descriptor 'rdbmsDescriptor'. The bean references this descriptor, but the descriptor does not contain an entry for this bean.

Description	Unable to find bean 'ejbName' in RDBMS CMP deployment descriptor 'rdbmsDescriptor'. The bean references this descriptor, but the descriptor does not contain an entry for this bean.
Cause	See the error message body.
Action	See the error message body.

BEA-011050

Error: Unable to find bean 'ejbName' in an RDBMS CMP deployment descriptor.

Description	Unable to find bean 'ejbName' in an RDBMS CMP deployment descriptor.
Cause	See the error message body.
Action	See the error message body.

BEA-011051

Error: Finder Collection in 'sourceName' is NULL.

Description	Finder Collection in 'sourceName' is NULL.
Cause	See the error message body.
Action	See the error message body.

BEA-011052

Error: The deployment descriptor for an EJB 2.0 CMP bean conforms to the wrong document type. A common error is to specify an EJB 1.1 deployment descriptor by mistake. The RDBMS CMP deployment descriptor for an EJB 2.0 CMP bean must reference one of the following valid XML public ids:

Description	The deployment descriptor for an EJB 2.0 CMP bean conforms to the wrong document type. A common error is to specify an EJB 1.1 deployment descriptor by mistake. The RDBMS CMP deployment descriptor for an EJB 2.0 CMP bean must reference one of the following valid XML public ids:
Cause	See the error message body.
Action	See the error message body.

BEA-011053

Error: Error 'sourceName' received null when trying to get CMPBeanDescriptor for 'ejbName'.

Description	Error 'sourceName' received null when trying to get CMPBeanDescriptor for 'ejbName'.
Cause	See the error message body.
Action	See the error message body.

BEA-011054

Error: Duplicate 'type' 'Name' found. The 'type' is defined twice in two of the following descriptor files:

Description	Duplicate 'type' 'Name' found. The 'type' is defined twice in two of the following descriptor files:
Cause	See the error message body.
Action	See the error message body.

BEA-011055

Error: Error deploying the EJB 'ejb', the JNDI name 'jndiName' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.

Description	Error deploying the EJB 'ejb', the JNDI name 'jndiName' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Cause	See the error message body.
Action	See the error message body.

BEA-011056

Error: The EJB module 'moduleName' cannot be deployed because it needs to be recompiled. Normally, this recompilation would happen automatically during the deployment process but since this is a pinned deployment, automatic recompilation has been disabled to ensure classes are kept in sync across the cluster. To proceed, you can either target this deployment to the entire cluster, instead of a subset of servers, or manually recompile this application using the weblogic.appc tool and redeploy.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011057

Warning: The table 'tableName' was created by the user. The container does not drop or alter user created tables. The container would verify the table in this case.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011058(retired)

Warning: In production mode the options ''DropAndCreate'',''DropAndCreateAlways'' and ''AlterOrCreate'' are ignored.The container would verify the table in this case.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011059

Warning: The container was unable to create the ddl file.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011060

Error: The container was unable to determine the java.sql.Types of database columns.

Description	The container was unable to determine the java.sql.Types of database columns for an unknown reason.Please try redeploying your bean.
Cause	See the error message body.
Action	See the error message body.

BEA-011061

Info: Stack trace associated with message id follows: \n

Description	A stack trace is being printed for an exception that occurred.
Cause	An error condition was reported.
Action	Look for the associated exception in the log or your program to see what the results are. I n general, this stack trace will help with debugging an existing problem.

BEA-011062

Info: The following exception has occurred: \n

Description	A stack trace is being printed for an exception that occurred.
Cause	An error condition was reported.
Action	This stack trace will help with debugging an existing problem.

BEA-011063

Error: Stateless session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method signature of EJB 'ejbName' either returned or threw an Exception without properly completing a transaction.

Description	The specified stateless session bean method did not complete a UserTransaction that it started. The EJB spec requires that stateless session beans that use bean managed transactions either commit or rollback any transaction started by a method before the method exits.
Cause	A transaction started by the stateless session bean method did not complete before the method completed.
Action	Check the bean code to determine what caused the transaction to not commit or rollback and fix it. Pay special attention to any Exceptions that may be thrown by the method, causing commit or rollback calls to be skipped. Finally blocks can be used to ensure transactions are properly completed in all situations.

BEA-011064(retired)

Error: The ORACLE SEQUENCE named 'sequence' with INCREMENT 'increment' \n was not found in the database

Description	see message body
Cause	see message body
Action	Examine the tag \nre-examine the and verify that this is the correct name of the ORACLE SEQUENCE \n re-examine the and verify that this is the correct size of the SEQUENCE INCREMENT value

BEA-011065(retired)

Error: The ORACLE SEQUENCE named 'sequence' does not have INCREMENT value 'increment' \n in the database

Description	see message body
Cause	see message body
Action	in the tag \n re-examine the and verify that this is the correct size of the SEQUENCE INCREMENT value

BEA-011066(retired)

Error: During EJB deployment, error(s) were encountered while setting up The ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011067(retired)

Warning: In production mode the options ''DropAndCreate'',''DropAndCreateAlways'' and ''AlterOrCreate'' are ignored. The container would verify the Oracle sequence in this case.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011068(retired)

Error: During EJB deployment, error(s) were encountered while attempting to CREATE the ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011069(retired)

Error: During EJB deployment, error(s) were encountered while attempting to ALTER the ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011070

Warning: In the , for 'ejbName', some (s) are defined but are not used in any , or s. The (s) of the unreferenced (s) are: 'fieldGroupList'

Description	see message body
Cause	see message body
Action	see message body

BEA-011071

Warning: In the , for 'ejbName', some (s) are defined but are not used in any . The (s) of the unreferenced (s) are: 'fieldGroupList'

Description	see message body
Cause	see message body
Action	see message body

BEA-011072

Error: Unable to bind EJB Local Home Interface to the JNDI name: localJndiName.

Description	Unable to bind EJB Local Home Interface to the JNDI name: localJndiName.
Cause	See error message body.
Action	See error message body.

BEA-011073

Error: An error occurred while the EJB container was attempting to obtain information about the table 'tableName' from the database. This information is necessary to validate the mapping between the fields of the EJB 'ejbName' and the table. The exception is: error

Description	When a CMP entity bean is deployed, the EJB container must query the database table the CMP bean maps to to ensure the EJBs fields map to the table columns correctly. An error occurred when the container was attempting to retrieve this information from the database.
Cause	The most likely cause is an error communicating with the database. The error message should include the specific error message.
Action	The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure you are using a supported database.

BEA-011074

Error: In EJB 'ejbName', application called createXXX() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.

Description	In EJB 'ejbName', application called createXXX() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.
Cause	See error message body.
Action	See error message body.

BEA-011075

Error: In EJB 'ejbName', application called remove() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.

Description	In EJB 'ejbName', application called remove() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.
Cause	See error message body.
Action	See error message body.

BEA-011076

Error: Unable to deploy the EJB 'ejbName' because the database table 'tableName' is not accessible. Please ensure that this table exists and is accessible.

Description	The specified entity bean depends on a database table that was not accessible at the time of deployment. The most likely cause is that the database table does not exist. Note that the EJB container can be configured to automatically create any necessary database tables when the server is in development mode. See the create-default-dbms-tables element of the WebLogic CMP descriptor for details. Note that tables will not automatically be created if the server is in production mode.
Cause	A necessary database table was not accessible.
Action	Ensure the database table exists and is accessible.

BEA-011077

Warning: The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode so no database tables will be created or altered.

Description	The WebLogic CMP descriptor for the EJB deployment contains settings for automatically creating or altering database tables during deployment. However, this feature is only enabled when the server is in development mode. Since the server is in production mode, the feature is disabled, which may affect the EJB deployment. See the create-default-dbms-tables element of the CMP deployment descriptor for details.
Cause	The server is in production mode so the create-default-dbms-tables settings are being ignored.
Action	No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.

BEA-011078

Info: An exception occurred while starting the freepool idle timeout timer for ejb: 'ejbName', 'exceptionMsg'.

Description

The bean freepool will function but without the idle timeout feature.

BEA-011079

Info: An exception occurred while stopping the freepool idle timeout timer for ejb: 'ejbName', 'exceptionMsg'.

Description

The idle timeout timer will continue to fire.

BEA-011080

Info: An exception occurred while starting the Cache idle timeout timer for cache: 'cacheName', 'exceptionMsg'.

Description

The Cache will function but without the idle timeout feature.

BEA-011081

Info: An exception occurred while stopping the Cache idle timeout timer for cache: 'cacheName', 'exceptionMsg'.

Description

The idle timeout timer will continue to fire.

BEA-011082

Error: Error: The message-destination-link 'destLink' for the message-driven bean 'ejbName' in the application module 'jarName' could not be resolved. The target message-destination for the message-driven bean 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-011083

Error: The EJB specification prohibits stateful session beans from using the TimerService.

Description	The EJB specification prohibits stateful session beans from using the EJB TimerService. An IllegalStateException is thrown by the EJB container when a stateful session bean illegally attempts to invoke the getTimerService() method on its EJBContext.
Cause	An illegal call to the getTimerService() method on the stateful session beans SessionContext.
Action	Correct the stateful session bean code so it does not call the getTimerService() method from the bean class.

BEA-011084

Error: This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method annotated with @Timeout.

Description	EJB classes must implement the javax.ejb.TimedObject interface in order to use the EJB TimerService. An IllegalStateException is thrown by the EJB container when an EJB does not implement the TimedObject interface and illegally attempts to invoke the getTimerService() method on its EJBContext.
Cause	An illegal call to the getTimerService() method on the EJBContext.
Action	Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure it does not call the getTimerService() method on the EJBContext.

BEA-011085

Error: This Timer has either expired or been canceled and therefore cannot be invoked.

Description	Once a Timer has been canceled or expired, it can no longer be invoked. The EJB specification requires the EJB container to throw a NoSuchObjectLocalException in such cases.
Cause	An illegal call to a Timer object after the Timer had expired or was canceled.
Action	Ensure your bean class does not invoke expired or canceled Timers.

BEA-011086

Error: The Timer associated with this TimerHandle has either expired or been canceled.

Description	Once a Timer has expired or been canceled, all associated TimerHandles are invalid. The EJB specification requires the EJB container to throw a NoSuchObjectLocalException when an attempt is made to obtain an expired or canceled Timer from a TimerHandle.
Cause	The Timer associated with the TimerHandle has expired or been canceled.
Action	No action required.

BEA-011087

Error: This TimerHandle is being invoked outside the context of the application it was created. Since timers are local objects, they can only be called from within the same application in which they were created.

Description	TimerHandles are only valid in the context of the application they are created in. Invoking a TimerHandle outside of the application will result in this error.
Cause	This TimerHandle is being invoked outside the context of the application it was created.
Action	Ensure your application does not pass any TimerHandle references outside the scope of the application.

BEA-011088

Error: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB 'ejbName'.

Description	This message indicates that an Exception or Error was either thrown from the ejbTimeout method or thrown from the EJB Container code while processing a timer Expiration.
Cause	This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.
Action	All Exceptions thrown while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, i.e. has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.

BEA-011089

Error: The following error occurred while attempting to remove an EJB Timer from the persistent store for EJB 'ejbName'.

Description	This message indicates that an Exception or Error was thrown while removing an EJB Timer from the underlying persistent store. This is a very serious error as it can lead to unexpected Timer expirations in the future.
Cause	This is an unexpected error so the cause is unknown. The accompanying Exception and stack trace should provide information as to the cause of the error.
Action	This cause of this error should be investigating and resolved promptly.

BEA-011090

Error: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB 'ejbName'.

Description	This message indicates that an Exception or Error was thrown from the EJB Container while preparing to invoke the ejbTimeout method.
Cause	This is an unexpected error so the cause is unknown. The accompanying Exception and stack trace should provide information as to the cause of the error.
Action	All Exceptions thrown while attempting to invoke the ejbTimeout method should be investigated and resolved.

BEA-011091

Warning: The table 'tableName' cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.

Description	When a trigger is associated with a table, the container will not attempt to drop or create the table. Dropping the table could result in the associated trigger being dropped. Creating the table may allow the deployment to succeed but the application would not function properly without the missing trigger. If a trigger is associated with a table, the user must manually create the database table and associated trigger. See the error message body.
Cause	See the error message body.
Action	To suppress this warning, the user can set the create-default-dbms-tables value in the RDBMS deployment descriptor to 'Disabled'.

BEA-011092

Warning: In production mode the options 'DropAndCreate','DropAndCreateAlways' and 'AlterOrCreate' are ignored. The container will only attempt to verify the existence and increment value of the sequence 'seqName'.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011093

Error: The SEQUENCE named 'sequence' with INCREMENT 'increment' was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.

Description	see message body
Cause	see message body
Action	Examine the tag in the CMP deployment descriptor. In particular, re-examine the and verify that this is the correct name of the SEQUENCE. Also, re-examine the and verify that this is the correct size of the SEQUENCE INCREMENT value

BEA-011094

Error: The SEQUENCE named 'sequence' does not have INCREMENT value of 'increment' in the database as specified in the CMP deployment descriptor. Please either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.

Description	see message body
Cause	see message body
Action	In the tag of the CMP deployment descriptor, re-examine the and verify that this is the correct size of the SEQUENCE INCREMENT value.

BEA-011095

Error: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011096

Error: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011097

Error: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'

Description	see message body
Cause	see message body
Action	see message body

BEA-011098

Error: No generated primary key was returned from the database insert statement as expected. Please verify the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.

Description	see message body
Cause	This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that doesn't support the getGeneratedKeys() method on java.sql.Statement.
Action	Verify the primary key column in the database is marked as an IDENTITY column (or a functional equivalent is setup for the column such as a database trigger to insert a value into the primary key column).

BEA-011099

Error: Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.

Description	see message body
Cause	This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.
Action	Verify the database table corresponding to the EJB only has a single generated column.

BEA-011100

Error: Automatic Key Generation: Error encountered while attempting setup and verify SEQUENCE TABLE tableName.

Description	Automatic Key Generation: Error encountered while attempting setup and verify SEQUENCE TABLE tableName.
Cause	See the error message body.
Action	See the error message body.

BEA-011101

Error: Automatic Key Generation Error: Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.

Description	Automatic Key Generation Error: Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.
Cause	See the error message body.
Action	See the error message body.

BEA-011102

Error: Automatic Key Generation Error: Error while attempting to BEGIN a new transaction prior to FETCH of next key from Sequence Table: sqlException.

Description	Automatic Key Generation Error: Error while attempting to BEGIN a new transaction prior to FETCH of next key from Sequence Table: sqlException.
Cause	See the error message body.
Action	See the error message body.

BEA-011103

Error: Automatic Key Generation Error: attempted to UPDATE or QUERY SEQUENCE TABLE tableName, but encountered SQLException sqlException.

Description	Automatic Key Generation Error: attempted to UPDATE or QUERY SEQUENCE TABLE tableName, but encountered SQLException sqlException.
Cause	See the error message body.
Action	See the error message body.

BEA-011104

Error: Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to SEQUENCE TABLE tableName, but encountered Exception exception.

Description	Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to SEQUENCE TABLE tableName, but encountered Exception exception.
Cause	See the error message body.
Action	See the error message body.

BEA-011105

Error: Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.

Description	Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.
Cause	See the error message body.
Action	See the error message body.

BEA-011106

Error: Invoking the set method of a cmp-field, configured to have a dbms-default-value in the WebLogic CMP deployment descriptor, is not allowed before the bean instance has been inserted into the database. The actual time in which the database insert occurs is dependent on several factors including whether batching or order-database-operations are enabled as well as the value of the delay-database-insert-until element of the WebLogic CMP deployment descriptor. Please refer to the documentation for details.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011107

Error: Illegal attempt to invoke an EJB Timer instance from the ejbCreate() method of an EJB. The EJB specification specifically disallows invocations of Timers from ejbCreate methods.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011108

Error: Illegal attempt to invoke an EJB Timer instance from the afterCompletion() method of a stateful session bean. The EJB specification specifically disallows invocations of Timers from the afterCompletion method.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-011109

Error: Failed to register JACC policy context handlers for the ejb container

Description	Failed to register JACC policy context handlers for the ejb container
Cause	Unexpected error
Action	See the error message body.

BEA-011110

Warning: The SEQUENCE named 'sequence' has key-cache-size set to 'increment' which is lesser than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.

Description	see message body
Cause	see message body
Action	in the tag re-examine the and verify that it is set correctly.

BEA-011111

Error: The SEQUENCE named 'sequence' has key-cache-size set to 'increment' which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.

Description	see message body
Cause	see message body
Action	in the tag re-examine the and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.

BEA-011112

Error: Error initializing the EJB Timer store for the EJB 'displayName'. The weblogic-ejb-jar.xml deployment descriptor or annotation for this EJB contains a persistent-store-logical-name setting but no persistent store with the logical name 'logicalStoreName' could be found on the server 'serverName'.

Description	see message body
Cause	see message body
Action	Ensure a persistent store with the given logical store name exists on the specified server. Alternatively, you can remove the logical store name from your weblogic-ejb-jar.xml deployment descriptor, causing each servers default store to be used.

BEA-011113

Error: Error: The Message Driven Bean 'displayName', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.

Description	see message body
Cause	see message body
Action	Ensure the Message Driven Bean (MDB) is mapped to a message destination. This can be done in the ejb-jar.xml descriptor by specifying a message-destination-link for the MDB. A message destination can be set in the weblogic-ejb-jar.xml inside the message-driven-descriptor element. Use the destination-resource-link to map the MDB to an application-scoped JMS destination. The destination-jndi-name element can be used to map the MDB to the JNDI name of a JMS destination. Finally, the resource-adapter-jndi-name element can be used to map the MDB to the JNDI name of a JCA resource adapter.

BEA-011114

Error: Error: For EJB modules, deployment plan overrides are not supported with DTD based deployment descriptors. The EJB module 'module' is attempting to apply a deployment plan to DTD based descriptors. Please update your EJB deployment descriptors to be schema based before attempting to apply the deployment plan override to this module. The weblogic.DDConverter utility can be used to automatically update your descriptors.

Description	see message body
Cause	see message body
Action	Run the weblogic.DDConverter utility on your application to update the deployment descriptors. After the descriptors are updated, the deployment plan overrides can be applied to the EJB module properly.

BEA-011115

Error: In EJB 'ejbName', application called setXXX() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.

Description	In EJB 'ejbName', application called setXXX() method of a bean that uses ReadOnly concurrency. This operation is not allowed. Use Database or Optimistic concurrency instead.
Cause	See error message body.
Action	See error message body.

BEA-011116

Error: Error while reading 'META-INF/ejb-jar.xml' or 'fileName'. The error was:\n errorMsg.

Description	Error while reading 'META-INF/ejb-jar.xml' or 'fileName'. The error was:\n errorMsg.
Cause	See the error message body.
Action	See the error message body.

BEA-011117

Error: The EJB 'ejbName' has a type-as-principal-name configured with higher privileges than the user performing the deployment. This EJB must either be deployed by a server Administrator or the EJB must be modified so it is not configured to run with higher privileges than the user deploying it.

Description	We detected a situation where a user tried to deploy an EJB 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-011118

Error: The EJB 'ejbName' has a type-as-principal-name 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 EJB 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-011119

Error: Error in CMP EJB ejbName. When loading a bean from the database the optimistic column 'columnName' for table 'tableName' was null. This is not allowed.

Description	We detected a null value for an optimistic column. If you are using a database trigger make sure that the trigger initializes the optimistic column when a row is inserted.
Cause	See the error message body.
Action	See the error message body.

BEA-011120

Warning: The CMP EJB ejbName has enable-batch-operations set to true, however the update queries are not suitable for batching. Batched operations are turned off for this batch and the queries shall be executed with multiple update statements.

Description	The CMP EJB ejbName has enable-batch-operations set to true, however the update queries are not suitable for batching. Batched operations are turned off for this batch and the queries shall be executed with multiple update statements.
Cause	See the error message body
Action	No action is required.

BEA-011121

Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.

Description	Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.
Cause	See the error message body.
Action	Add the plugin-class 'pluginClass' in the server classpath

BEA-011122

Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be instantiated

Description	Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be instantiated
Cause	See the error message body.
Action	See the error message body.

BEA-011123

Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.

Description	Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.
Cause	See the error message body.
Action	See the error message body.

BEA-011124

Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' does not implement weblogic.ejb.spi.SecurityPlugin.

Description	Error in MDB EJB ejbName. The plugin-class 'pluginClass' does not implement weblogic.ejb.spi.SecurityPlugin.
Cause	See the error message body.
Action	Make the plugin-class 'pluginClass' implement weblogic.ejb.spi.SecurityPlugin.

BEA-011125

Error: An unexpected error was encountered while attempting to remove any EJB Timers from the persistent store for the EJB 'ejbName'.

Description	When an application is undeployed, we attempt to remove any EJB timers associated with that application from the persistent store. Also, when an application is newly deployed, we remove old timers that may have failed to be removed during undeployment. An unexpected error occurred as we attempted to remove any such timers.
Cause	See the error message body.
Action	See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.

BEA-011126

Info: The same Throwable has consecutively caused the expiration to fail for the EJB timer: timerInfo. Consecutive errors of this type will no longer be logged for the current timer expiration.

Description	By default, an Exception thrown out of the ejbTimeout method of an EJB will cause the timeout to be retried immediately. To prevent duplicate error messages in the server log, we wont report consecutive timeout failures caused by the same Exception. This message indicates that the same Throwable has caused the timeout to fail consecutively and that we skipped logging some error messages.
Cause	See the error message body.
Action	Investigate what caused the ejbTimeout method to fail. The original Throwable will be logged in a previous error message.

BEA-011127

Error: Error deserializing one or more EJB timers from the persistent store for the EJB deployment 'ejbModule'. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: error

Description	When an EJB that implements javax.ejb.TimedObject deploys, the EJB container instantiates any previously created EJB timers from the persistent store. The container was unable to deserialize one or more of the EJB timers. A common cause of this error is an incompatible Serializable class change in your application.
Cause	See the error message body for details.
Action	If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the Serializable class associated with the EJB timer and redeploy the application. This would allow the EJB timer to be deserialized.

BEA-011128

Error: Error creating an instance of the EJB 'displayName': error

Description	The EJB container encountered an unexpected error while trying to instantiate a new instance of the specified EJB.
Cause	See the error message body for details.
Action	This error may be due to a configuration issue or a bug in the EJB container. Please see the specific error message for details.

BEA-011129

Error: Error deploying EJB 'displayName' to server 'serverName'. This EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.

Description	EJBs that use Clustered EJB Timers can only be deployed to servers that are part of a cluster. During deployment, the EJB container detected that the current server is not part of a cluster.
Cause	It is illegal to deploy an EJB that uses Clustered EJB Timers to a server that is not part of a cluster.
Action	You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or ensure that any servers you deploy the EJB to are part of a cluster.

BEA-011130

Error: Error deploying EJB 'displayName'. This EJB is configured to use the clustered EJB Timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.

Description	EJBs that use Clustered EJB Timers can only be deployed to servers that are part of a cluster. In addition, the data-source-for-job-scheduler attribute of the cluster must be set. While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.
Cause	While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.
Action	You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or configure the data-source-for-job-scheduler attribute for your cluster.

BEA-011131(retired)

Error: Error deploying EJB 'displayName'. While binding a business interface to JNDI the following error occurred: e

Description	While deploying the EJB mentioned in the error message, the EJB container was unable to bind one of the remote business interfaces of the EJB into JNDI.
Cause	See the specific error for details.
Action	The action will depend on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.

BEA-011132

Error: Error deploying EJB 'displayName'. While binding a business interface to the JNDI name 'jndiName', the following error occurred: e

Description	While deploying the EJB mentioned in the error message, the EJB container was unable to bind one of the remote business interfaces of the EJB into JNDI.
Cause	See the specific error for details.
Action	The action will depend on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.

BEA-011133

Error: Unable to bind Business Interface to the JNDI name: jndiName, throw exception e.

Description	Unable to bind Business Interface to the JNDI name: jndiName, throw exception e.
Cause	See error message body.
Action	See error message body.

BEA-011134

Error: Unable to bind Local Business Interface to the JNDI name: localJndiName, throw exception e.

Description	Unable to bind Local Business Interface to the JNDI name: localJndiName, throw exception e.
Cause	See error message body.
Action	See error message body.

BEA-012000

Error: Method 'methodName' not found in interface 'sourceName'.

Description	Method 'methodName' not found in interface 'sourceName'.
Cause	See the error message body.
Action	See the error message body.

BEA-012001

Error: While processing parameters for Automatic Key Generation. For generator-type: generatorType, the generator-name tag must specify the requiredSpecifier name.

Description	While processing parameters for Automatic Key Generation. For generator-type: generatorType, the generator-name tag must specify the requiredSpecifier name.
Cause	See the error message body.
Action	See the error message body.

BEA-012002(retired)

Error: Error occurred while processing parameters for Automatic Key Generation. Unknown generator-type: generatorType. Allowed values are: ORACLE, SQL_SERVER, NAMED_SEQUENCE_TABLE.

Description	Error occurred while processing parameters for Automatic Key Generation. Unknown generator-type: generatorType. Allowed values are: ORACLE, SQL_SERVER, NAMED_SEQUENCE_TABLE.
Cause	See the error message body.
Action	See the error message body.

BEA-012003(retired)

Error: Error occurred while processing parameters for Automatic Key Generation. Encountered unknown : generatorType. /n/nAction, respecify the using one of the legal values: Oracle | SQLServer | namedSequenceTable.

Description	Error occurred while processing parameters for Automatic Key Generation. Encountered unknown : generatorType. /n/nAction, respecify the using one of the legal values: Oracle \| SQLServer \| namedSequenceTable.
Cause	See the error message body.
Action	See the error message body.

BEA-012004

Error: When Automatic Key Generation is enabled, the Primary Key cannot be part of the Foreign Key to another bean.

Description	When Automatic Key Generation is enabled, the Primary Key cannot be part of the Foreign Key to another bean.
Cause	See the error message body.
Action	See the error message body.

BEA-012005

Error: In 'source', unable to load Class 'className'.

Description	In 'source', unable to load Class 'className'.
Cause	See the error message body.
Action	See the error message body.

BEA-012006

Error: Field 'field' not found in class 'class'.

Description	Field 'field' not found in class 'class'.
Cause	See the error message body.
Action	See the error message body.

BEA-012007

Error: Could not generate Finder method code for type 'finder' due to EJBCException: 'exceptionMessage'.

Description	Could not generate Finder method code for type 'finder' due to EJBCException: 'exceptionMessage'.
Cause	See the error message body.
Action	See the error message body.

BEA-012008

Error: NULL finder in 'target'.

Description	NULL finder in 'target'.
Cause	See the error message body.
Action	See the error message body.

BEA-012009

Error: Could not find cmr-field for Remote Relationship Bean involved in Query. Could not find it in either Bean Param for Remote Bean or RemoteFinderNode: 'target'.

Description	Could not find cmr-field for Remote Relationship Bean involved in Query. Could not find it in either Bean Param for Remote Bean or RemoteFinderNode: 'target'.
Cause	See the error message body.
Action	See the error message body.

BEA-012010(retired)

Error: Could not find any HomeClass Name for Finder Expression in Finder: 'finder'.

Description	Could not find any HomeClass Name for Finder Expression in Finder: 'finder'.
Cause	See the error message body.
Action	See the error message body.

BEA-012011(retired)

Error: Could not find any Remote Finder Node for Finder: 'finder'.

Description	Could not find any Remote Finder Node for Finder: 'finder'.
Cause	See the error message body.
Action	See the error message body.

BEA-012012

Error: Could not find any RemoteHomeName checked for RemoteFinderNode or Remote ParamNode and found neither for Finder: 'finder'.

Description	Could not find any RemoteHomeName checked for RemoteFinderNode or Remote ParamNode and found neither for Finder: 'finder'.
Cause	See the error message body.
Action	See the error message body.

BEA-012013

Error: Method 'method' in interface 'interface' has wrong Parameter count, expected: expectedParamCount.

Description	Method 'method' in interface 'interface' has wrong Parameter count, expected: expectedParamCount.
Cause	See the error message body.
Action	See the error message body.

BEA-012014

Error: Remote Finder in Finder 'finder': Remote Finder Name is null.

Description	Remote Finder in Finder 'finder': Remote Finder Name is null.
Cause	See the error message body.
Action	See the error message body.

BEA-012015

Error: Expected to get 'target' for finder 'finder', but we got null instead.

Description	Expected to get 'target' for finder 'finder', but we got null instead.
Cause	See the error message body.
Action	See the error message body.

BEA-012016

Error: Expected to get entry in beanMap for 'ejbName', but got null instead.

Description	Expected to get entry in beanMap for 'ejbName', but got null instead.
Cause	See the error message body.
Action	See the error message body.

BEA-012017

Error: Error while generating target.

Description	Error while generating target.
Cause	See the error message body.
Action	See the error message body.

BEA-012018(retired)

Error: Error while compiling Query with Remote Finder unknown Remote Finder Command: 'command'.

Description	Error while compiling Query with Remote Finder unknown Remote Finder Command: 'command'.
Cause	See the error message body.
Action	See the error message body.

BEA-012019

Error: Could not produce production rule for target.

Description	Could not produce production rule for target.
Cause	See the error message body.
Action	See the error message body.

BEA-012020

Error: In Finder 'finderName', could not get Class for cmpField 'field'.

Description	In Finder 'finderName', could not get Class for cmpField 'field'.
Cause	See the error message body.
Action	See the error message body.

BEA-012021

Error: Error: No persistence-type element was declared with the type-identifier 'id' and 'version' for the EJB 'ejbName'. Make sure your persistence-use declaration matches up with one of your persistence-type declarations for this EJB in the weblogic-ejb-jar.xml file.

Description	Error: No persistence-type element was declared with the type-identifier 'id' and 'version' for the EJB 'ejbName'. Make sure your persistence-use declaration matches up with one of your persistence-type declarations for this EJB in the weblogic-ejb-jar.xml file.
Cause	See the error message body.
Action	See the error message body.

BEA-012022

Error: In weblogic-ejb-jar.xml, an entity-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Entity bean in ejb-jar.xml.

Description	In weblogic-ejb-jar.xml, an entity-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Entity bean in ejb-jar.xml.
Cause	See the error message body.
Action	See the error message body.

BEA-012023

Error: In weblogic-ejb-jar.xml or annotation, a stateless-session-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Stateless Session bean in ejb-jar.xml or annotation.

Description	In weblogic-ejb-jar.xml, a stateless-session-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Stateless Session bean in ejb-jar.xml.
Cause	See the error message body.
Action	See the error message body.

BEA-012024

Error: In weblogic-ejb-jar.xml or annotation, a stateful-session-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Stateful Session bean in ejb-jar.xml or annotation.

Description	In weblogic-ejb-jar.xml, a stateful-session-descriptor element was found for EJB 'ejbName'. This EJB was not declared as an Stateful Session bean in ejb-jar.xml.
Cause	See the error message body.
Action	See the error message body.

BEA-012025

Error: In weblogic-ejb-jar.xml or annotation, a message-driven-descriptor element was found for EJB 'ejbName'. This EJB was not declared as a Message-Driven bean in ejb-jar.xml or annotation.

Description	In weblogic-ejb-jar.xml, a message-driven-descriptor element was found for EJB 'ejbName'. This EJB was not declared as a Message-Driven bean in ejb-jar.xml.
Cause	See the error message body.
Action	See the error message body.

BEA-012026(retired)

Error: The ejb-ref 'ejbRefName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The ejb-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.

Description	The ejb-ref 'ejbRefName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The ejb-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
Cause	See the error message body.
Action	See the error message body.

BEA-012027(retired)

Error: EJB Entity Reference 'ejbName' has no JNDI name set. The JNDI name must be set in the WebLogic deployment descriptor 'relationship-descriptor' element.

Description	EJB Entity Reference 'ejbName' has no JNDI name set. The JNDI name must be set in the WebLogic deployment descriptor 'relationship-descriptor' element.
Cause	See the error message body.
Action	See the error message body.

BEA-012028(retired)

Error: The ejb-local-ref 'ejbName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The ejb-local-ref must be mapped to a JNDI name using the ejb-local-reference-description element of the weblogic-ejb-jar.xml descriptor.

Description	The ejb-local-ref 'ejbName' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The ejb-local-ref must be mapped to a JNDI name using the ejb-local-reference-description element of the weblogic-ejb-jar.xml descriptor.
Cause	See the error message body.
Action	See the error message body.

BEA-012029

Error: Error occurred while processing weblogic-rdbms-bean.xml file: 'fileName'. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean). EJB Name : 'ejbName'. XML Processor: 'xmlProcessor'.

Description	Error occurred while processing weblogic-rdbms-bean.xml file: 'fileName'. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean). EJB Name : 'ejbName'. XML Processor: 'xmlProcessor'.
Cause	See the error message body.
Action	See the error message body.

BEA-012030

Error: Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE 'publicId' not permitted. Only DOCTYPE 'correctDocType' permitted here.

Description	Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE 'publicId' not permitted. Only DOCTYPE 'correctDocType' permitted here.
Cause	See the error message body.
Action	See the error message body.

BEA-012031

Warning: The EJB 'ejbName' has a finder 'finderName' for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases. Use the WEBLOGIC-QL 'DISTINCT' clause instead. The container will automatically filter duplicates if necessary.

Description	The EJB 'ejbName' has a finder 'finderName' for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases. Use the EJB-QL 'DISTINCT' clause instead. The container will automatically filter duplicates if necessary.
Cause	See the error message body.
Action	See the error message body.

BEA-012032

Warning: Warning: for EJB ejbName, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is methodSig.

Description	Warning: for EJB ejbName, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The method referred to by the weblogic-query element is methodSig.
Cause	The weblogic-query element references a wrong or non-existent query method for this entity EJB.
Action	Remove the weblogic-query element or update it so that it references the correct query method.

BEA-012033

Info: Compiling generated EJB classes produced the following Java compiler output:\noutput

Description	When the EJB compiler is run, it generates wrapper classes for the EJBs. After it generates these classes, it invokes the Java compiler to compile them. The output from the Java compiler follows this log message. If the compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.
Cause	While compiling EJB generated classes, the Java compiler produced output.
Action	Typically, there is no action to take. The Java compiler output is printed for informational purposes. If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.

BEA-012034

Error: The message-destination 'destName' declared in the ejb-jar.xml deployment descriptor or annotation of the EJB module 'jarName', does not have a corresponding message-destination-descriptor element in the weblogic-ejb-jar.xml descriptor or corresponding annotation.

Description	Each logical message-destination declared in the ejb-jar.xml deployment descriptor must have a corresponding message-destination-descriptor element in the weblogic-ejb-jar.xml descriptor or corresponding annotation. The message-destination-descriptor maps the logical message-destination-name to the actual message destination.
Cause	A declared message-destination is not mapped correctly.
Action	Map the declared message-destination to the actual message destination using the message-destination-descriptor element in weblogic-ejb-jar.xml.

BEA-012035

Warning: The Remote interface method: 'method' in EJB 'ejbName' contains a parameter of type: 'parameterName' which is not Serializable. Though the EJB 'ejbName' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.

Description	EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is Serializable. As this parameter is not Serializable, the parameter will be passed by reference.
Cause	EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is Serializable. As this parameter is not Serializable, the parameter will be passed by reference.
Action	The parameter should implement the java.io.Serializable interface for it to be passed by value.

BEA-012036

Error: Compiling generated EJB classes produced the following Java compiler error message:\noutput

Description	When the EJB compiler is run, it generates wrapper classes for the EJBs. After it generates these classes, it invokes the Java compiler to compile them. The output from the Java compiler follows this log message. If the compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.
Cause	While compiling EJB generated classes, the Java compiler produced output.
Action	If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.

BEA-013000

Error: Finder: 'finderName', the SELECT clause for a finder must return a Bean. Non-Bean return types such as cmp-fields are not allowed. This EJB QL Query does not return a Bean 'ejbQuery'.

Description	Finder: 'finderName', the SELECT clause for a finder must return a Bean. Non-Bean return types such as cmp-fields are not allowed. This EJB QL Query does not return a Bean 'ejbQuery'.
Cause	See the error message body.
Action	See the error message body.

BEA-013001

Error: Finder: 'finderName', the SELECT clause for a finder must return an EJB of a type equal to the EJB for which the finder is written. Expected EJB: 'expectedEjbName' but instead found: 'foundEjbName'.

Description	Finder: 'finderName', the SELECT clause for a finder must return an EJB of a type equal to the EJB for which the finder is written. Expected EJB: 'expectedEjbName' but instead found: 'foundEjbName'.
Cause	See the error message body.
Action	See the error message body.

BEA-013002

Error: Expression 'exprType' has incorrect number of terms: termCount.

Description	Expression 'exprType' has incorrect number of terms: termCount.
Cause	See the error message body.
Action	See the error message body.

BEA-013003

Error: Expression 'exprType' requires a requirement.

Description	Expression 'exprType' requires a requirement.
Cause	See the error message body.
Action	See the error message body.

BEA-013004

Error: Parameters in EJB QL must be numbered 1 or greater. Finder 'finder' has a parameter numbered: 'badParamNum'. This must be corrected.

Description	Parameters in EJB QL must be numbered 1 or greater. Finder 'finder' has a parameter numbered: 'badParamNum'. This must be corrected.
Cause	See the error message body.
Action	See the error message body.

BEA-013005

Error: Cannot find a ParameterEntry for finder method: 'finder' in the method signature for the Finder at position: 'badParamNum'. Please double check your finder method signature and your EJB QL Parameter numbering.

Description	Cannot find a ParameterEntry for finder method: 'finder' in the method signature for the Finder at position: 'badParamNum'. Please double check your finder method signature and your EJB QL Parameter numbering.
Cause	See the error message body.
Action	See the error message body.

BEA-013006

Error: in 'inClause'; clause: could not get Class corresponding to cmp-field: 'cmpField' in path: 'id' for Bean: 'ejbName'.

Description	in 'inClause'; clause: could not get Class corresponding to cmp-field: 'cmpField' in path: 'id' for Bean: 'ejbName'.
Cause	See the error message body.
Action	See the error message body.

BEA-013007

Error: Error encountered while attempting to get target for for: 'exception'.

Description	Error encountered while attempting to get target for for: 'exception'.
Cause	See the error message body.
Action	See the error message body.

BEA-013008

Error: SELECT target for finder: 'finderName' must evaluate to be the EJB that owns the finder: 'owningBean'. Instead, the SELECT target evaluates to: 'foundBean'.

Description	SELECT target for finder: 'finderName' must evaluate to be the EJB that owns the finder: 'owningBean'. Instead, the SELECT target evaluates to: 'foundBean'.
Cause	See the error message body.
Action	See the error message body.

BEA-013009

Error: SELECT clause processing could NOT find JoinNode for 'id' in JoinTree. Please double check your EJB QL query for correctness.

Description	SELECT clause processing could NOT find JoinNode for 'id' in JoinTree. Please double check your EJB QL query for correctness.
Cause	See the error message body.
Action	See the error message body.

BEA-013010

Error: An EJB QL Query requires a SELECT clause at the beginning of the query.

Description	An EJB QL Query requires a SELECT clause at the beginning of the query.
Cause	See the error message body.
Action	See the error message body.

BEA-013011

Error: An EJB QL Query requires a FROM clause following the SELECT clause in the Query.

Description	An EJB QL Query requires a FROM clause following the SELECT clause in the Query.
Cause	See the error message body.
Action	See the error message body.

BEA-013012

Error: First term of range_variable_declaration 'id' cannot be a Path Expression. It can only be an abstract_schema_name.

Description	First term of range_variable_declaration 'id' cannot be a Path Expression. It can only be an abstract_schema_name.
Cause	See the error message body.
Action	See the error message body.

BEA-013013

Error: Could not get abstractSchemaName from ejb-jar.xml for comparison to input range_variable_declaration 'id'.

Description	Could not get abstractSchemaName from ejb-jar.xml for comparison to input range_variable_declaration 'id'.
Cause	See the error message body.
Action	See the error message body.

BEA-013014

Error: Could not get an abstract schema name from ejb-jar.xml for entity bean 'ejbName'. An abstract schema name is required.

Description	Could not get an abstract schema name from ejb-jar.xml for entity bean 'ejbName'. An abstract schema name is required.
Cause	See the error message body.
Action	See the error message body.

BEA-013015

Error: Could not find an entity EJB for abstract schema name, 'id', which is declared in a range variable declaration. Verify that an EJB is defined in the ejb-jar.xml descriptor with this abstract schema name.

Description	Could not find an entity EJB for abstract schema name, 'id', which is declared in a range variable declaration. Verify that an EJB is defined in the ejb-jar.xml descriptor with this abstract schema name.
Cause	See the error message body.
Action	See the error message body.

BEA-013016(retired)

Error: function argument must be a single valued path expression.

Description	function argument must be a single valued path expression.
Cause	See the error message body.
Action	See the error message body.

BEA-013017

Error: Exception occurred while trying to get last JoinNode in path for relationshipType. Path ID 'pathId' 'exceptionText'

Description	Exception occurred while trying to get last JoinNode in path for relationshipType. Path ID 'pathId' 'exceptionText'
Cause	See the error message body.
Action	See the error message body.

BEA-013018

Error: Expected a single Foreign Key Column for relationshipType in path expression: 'pathId'. Instead, found: foundSize

Description	Expected a single Foreign Key Column for relationshipType in path expression: 'pathId'. Instead, found: foundSize
Cause	See the error message body.
Action	See the error message body.

BEA-013019

Error: Bean: 'ejbName' cmr-field: 'cmrField' Error ! Attempt to call IS (NOT) NULL on a Collection_Valued_Path pointing to badRelType. Can only run on One-To-One or Many-To-One Relationship.

Description	Bean: 'ejbName' cmr-field: 'cmrField' Error ! Attempt to call IS (NOT) NULL on a Collection_Valued_Path pointing to badRelType. Can only run on One-To-One or Many-To-One Relationship.
Cause	See the error message body.
Action	See the error message body.

BEA-013020

Error: Cannot do IS [NOT] NULL evaluation on Path Expression: 'pathExpression'. IS [NOT] NULL expects an argument that is either a Path Expression that terminates in a cmp-field or in a cmr-field (for example: 'SELECT a FROM EJBA AS a WHERE a.cmrfield_b IS [NOT] NULL').

Description	Cannot do IS [NOT] NULL evaluation on Path Expression: 'pathExpression'. IS [NOT] NULL expects an argument that is either a Path Expression that terminates in a cmp-field or in a cmr-field (for example: 'SELECT a FROM EJBA AS a WHERE a.cmrfield_b IS [NOT] NULL').
Cause	See the error message body.
Action	See the error message body.

BEA-013021

Error: Could not find cmr-field in Bean: 'ejbNameFrom' that points to EJBean: 'ejbNameTo'.

Description	Could not find cmr-field in Bean: 'ejbNameFrom' that points to EJBean: 'ejbNameTo'.
Cause	See the error message body.
Action	See the error message body.

BEA-013022

Error: While compiling 'ejbqlOperation' on the pathExpression 'pathExpression', expected to find a foreign key column on Table 'fkTable', which points to a primary key on Table 'pkTable', but could not. Check the foreign key column mappings in the weblogic-relationship-role in your WebLogic RDBMS CMP descriptors.

Description	While compiling 'ejbqlOperation' on the pathExpression 'pathExpression', expected to find a foreign key column on Table 'fkTable', which points to a primary key on Table 'pkTable', but could not. Check the foreign key column mappings in the weblogic-relationship-role in your WebLogic RDBMS CMP descriptors.
Cause	See the error message body.
Action	See the error message body.

BEA-013023

Error: Bean: 'ejbName' cmr-field: 'cmrField' relationshipType, expected cmr-field to be a foreign key field but apparently it is not.

Description	Bean: 'ejbName' cmr-field: 'cmrField' relationshipType, expected cmr-field to be a foreign key field but apparently it is not.
Cause	See the error message body.
Action	See the error message body.

BEA-013024

Error: Bean: 'ejbName' cmr-field: 'cmrField' could not get Foreign Key Column Names for 'command'.

Description	Bean: 'ejbName' cmr-field: 'cmrField' could not get Foreign Key Column Names for 'command'.
Cause	See the error message body.
Action	See the error message body.

BEA-013025

Error: Error argument to 'command' must be a collection valued path expression.

Description	Error argument to 'command' must be a collection valued path expression.
Cause	See the error message body.
Action	See the error message body.

BEA-013026

Error: Error: could not get Join Table.

Description	Error: could not get Join Table.
Cause	See the error message body.
Action	See the error message body.

BEA-013027

Error: Error: could not get Foreign Key Table.

Description	Error: could not get Foreign Key Table.
Cause	See the error message body.
Action	See the error message body.

BEA-013028(retired)

Error: Left Hand argument to [NOT] MEMBER [OF] must be either a single_valued_path_expression or in input parameter.

Description	Left Hand argument to [NOT] MEMBER [OF] must be either a single_valued_path_expression or in input parameter.
Cause	See the error message body.
Action	See the error message body.

BEA-013029

Error: The type of the left hand argument to [NOT] MEMBER [OF] must be one of: \ninput variable (e.g. ?1) \nrange variable identifier declared in the FROM clause of this query or a parent of this query. \ncollection member identifier declared in the FROM clause of this query or a parent of this query. \nsingle_valued_navigation \n the type of the left hand argument 'val' is not any of these. \nAction, review the specification of the left hand argument and rewrite the query.

Description	The type of the left hand argument to [NOT] MEMBER [OF] must be one of: \ninput variable (e.g. ?1) \nrange variable identifier declared in the FROM clause of this query or a parent of this query. \ncollection member identifier declared in the FROM clause of this query or a parent of this query. \nsingle_valued_navigation \n the type of the left hand argument 'val' is not any of these. \nAction, review the specification of the left hand argument and rewrite the query.
Cause	See the error message body.
Action	See the error message body.

BEA-013030(retired)

Error: Right-hand argument to [NOT] MEMBER [OF] must be a collection_valued_path_expression.

Description	Right-hand argument to [NOT] MEMBER [OF] must be a collection_valued_path_expression.
Cause	See the error message body.
Action	See the error message body.

BEA-013031

Error: The type of the right-hand argument 'val' to [NOT] MEMBER [OF] must be: \ncollection_valued_path_expression \n. Review the specification of the right-hand argument and rewrite the query.

Description	The type of the right-hand argument to [NOT] MEMBER [OF] must be: \ncollection_valued_path_expression \n. Review the specification of the right-hand argument and rewrite the query.
Cause	See the error message body.
Action	See the error message body.

BEA-013032

Error: Could not get pkClass for pkField: 'field'.

Description	Could not get pkClass for pkField: 'field'.
Cause	See the error message body.
Action	See the error message body.

BEA-013033

Error: The left-hand argument to [NOT] MEMBER [OF] is of Interface: 'Lname'. The right-hand argument is a collection of interfaces of type: 'Rname'. The left-hand and right-hand interfaces are required to be of the same type, but apparently they are not.

Description	The left-hand argument to [NOT] MEMBER [OF] is of Interface: 'Lname'. The right-hand argument is a collection of interfaces of type: 'Rname'. The left-hand and right-hand interfaces are required to be of the same type, but apparently they are not.
Cause	See the error message body.
Action	See the error message body.

BEA-013034(retired)

Error: Could not get Table Alias List.

Description	Could not get Table Alias List.
Cause	See the error message body.
Action	See the error message body.

BEA-013035

Error: Expected a Boolean literal of TRUE or FALSE, but received neither.

Description	Expected a Boolean literal of TRUE or FALSE, but received neither.
Cause	See the error message body.
Action	See the error message body.

BEA-013036

Error: Could not obtain Table and Field for 'id'.

Description	Could not obtain Table and Field for 'id'.
Cause	See the error message body.
Action	See the error message body.

BEA-013037

Error: This is not a valid string_expression type. Refer to the EJB 2.0 spec 11.4 EJB QL BNF for valid definitions.

Description	This is not a valid string_expression type. Refer to the EJB 2.0 spec 11.4 EJB QL BNF for valid definitions.
Cause	See the error message body.
Action	See the error message body.

BEA-013038

Error: This is not a valid arithmetic_expression type. Refer to the EJB 2 .0 spec 11.4 EJB QL BNF for valid definitions.

Description	This is not a valid arithmetic_expression type. Refer to the EJB 2.0 spec 11.4 EJB QL BNF for valid definitions.
Cause	See the error message body.
Action	See the error message body.

BEA-013039

Error: Remote Interface cmrfield: 'cmrField' from bean 'ejbName' is not the terminal field in the path. A Remote Interface must be the final field.

Description	Remote Interface cmrfield: 'cmrField' from bean 'ejbName' is not the terminal field in the path. A Remote Interface must be the final field.
Cause	See the error message body.
Action	See the error message body.

BEA-013040

Error: Error Path Expression ends in x, not y.

Description	Error Path Expression ends in x, not y.
Cause	See the error message body.
Action	See the error message body.

BEA-013041

Error: The argument(s) to 'operator' must be cmp-fields or single-valued-path-expressions ending in a cmp-field. 'argument' is neither of these. Please re-examine your query.

Description	The argument(s) to 'operator' must be cmp-fields or single-valued-path-expressions ending in a cmp-field. 'argument' is neither of these. Please re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013042

Error: The Identifier 'argument' is neither a cmp-field nor a cmr-field. Re-examine your query.

Description	The Identifier 'argument' is neither a cmp-field nor a cmr-field. Re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013043

Error: TOKEN 'SPECIAL' 'specialName' has no counterpart in EJB QL. Finder Expressions are not supported. Cannot translate.

Description	TOKEN 'SPECIAL' 'specialName' has no counterpart in EJB QL. Finder Expressions are not supported. Cannot translate.
Cause	See the error message body.
Action	See the error message body.

BEA-013044(retired)

Error: Attempted to define the Identifier 'specialName' in an AS clause more than once. You may only define 'specialName' once.

Description	Attempted to define the Identifier 'specialName' in an AS clause more than once. You may only define 'specialName' once.
Cause	See the error message body.
Action	See the error message body.

BEA-013045

Error: The bean specified by identifier 'identifier' can only be tested against another bean of the same type. Re-examine your query and verify that 'identifier' is being compared to another bean of the same type.

Description	The bean specified by identifier 'identifier' can only be tested against another bean of the same type. Re-examine your query and verify that 'identifier' is being compared to another bean of the same type.
Cause	See the error message body.
Action	See the error message body.

BEA-013046

Error: A sub-query can only have one Select target. Apparently, there is a sub-query in this query that has more than one Select target. Re-examine your query.

Description	A sub-query can only have one Select target. Apparently, there is a sub-query in this query that has more than one Select target. Re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013047

Error: ORDERBY in WLQL takes actual DBMS Column Names but ORDERBY in EJB QL takes Abstract Schema Name. Cannot translate from WLQL to EJB QL.

Description	ORDERBY in WLQL takes actual DBMS Column Names but ORDERBY in EJB QL takes Abstract Schema Names. Cannot translate from WLQL to EJB QL.
Cause	See the error message body.
Action	See the error message body.

BEA-013048

Error: Sub-queries that SELECT beans cannot be compared to Variables (e.g. ?1). This is not supported.

Description	Sub-queries that SELECT beans cannot be compared to Variables (e.g. ?1). This is not supported.
Cause	See the error message body.
Action	See the error message body.

BEA-013049

Error: The identifier 'id', of localInterface Type 'idInterface', can only be tested against another bean with the same localInterface type. ?variableNo is of localInterface type 'variableInterface'. This does not match the type of the identifier 'id'. Re-examine your query.

Description	The identifier 'id', of localInterface Type 'idInterface', can only be tested against another bean with the same localInterface type. ?variableNo is of localInterface type 'variableInterface'. This does not match the type of the identifier 'id'. Re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013050

Error: Sub-queries are required to have a 'id' clause. One of the Sub-queries in the Main Query seems to be missing a 'id' clause. Please re-examine your query.

Description	Sub-queries are required to have a 'id' clause. One of the Sub-queries in the Main Query seems to be missing a 'id' clause. Please re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013051

Error: Could not find a Range Variable as defined in an 'AS' declaration that refers to the root of the path expression: 'id'. Please check your Query and verify that you have defined a 'FROM (abstract_schema_name) AS id' in your Query.

Description	Could not find a Range Variable as defined in an 'AS' declaration that refers to the root of the path expression: 'id'. Please check your Query and verify that you have defined a 'FROM (abstract_schema_name) AS id' in your Query.
Cause	See the error message body.
Action	See the error message body.

BEA-013052

Error: \nProblem, range variable identifier 'id' is not declared in the FROM clause of this query or in any parent query. \n\nAction, review the query, and check whether 'id' needs to be declared as a range variable identifier as in 'FROM SomeBean AS id'.

Description	\nProblem, range variable identifier 'id' is not declared in the FROM clause of this query or in any parent query. \n\nAction, review the query, and check whether 'id' needs to be declared as a range variable identifier as in 'FROM SomeBean AS id'.
Cause	See the error message body.
Action	See the error message body.

BEA-013053

Error: 'op' argument is not of type IDENTIFIER or INTEGER. Found an argument of type 'bad_type'. Re-examine your query.

Description	'op' argument is not of type IDENTIFIER or INTEGER. Found an argument of type 'bad_type'. Re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013054

Error: The op clause cannot be used in java.sql.ResultSet queries that return beans. A query using op can only have cmp-fields or aggregates of cmp-fields (e.g. SELECT orders.date AVG(orders.amount)) in its SELECT list.

Description	The op clause cannot be used in java.sql.ResultSet queries that return beans. A query using op can only have cmp-fields or aggregates of cmp-fields (e.g. SELECT orders.date AVG(orders.amount)) in its SELECT list.
Cause	See the error message body.
Action	See the error message body.

BEA-013055

Error: ejbSelects that return java.sql.ResultSet, cannot have Beans as SELECT targets. Only cmp-fields or aggregates (AVG, MAX, etc) are allowed. Found a SELECT argument 'target' of type 'bad_type', which does not meet this criteria. Please re-examine your query.

Description	ejbSelects that return java.sql.ResultSet cannot have Beans as SELECT targets. Only cmp-fields or aggregates (AVG, MAX, etc) are allowed. Found a SELECT argument 'target' of type 'bad_type', which does not meet this criteria. Please re-examine your query.
Cause	See the error message body.
Action	See the error message body.

BEA-013056(retired)

Error: Cannot translate from WLQL to EJB QL. It is suggested that you use the following EJB QL: FROM abstract-schema-name AS X. Usage of EJB QL of this form will result in a Finder with no WHERE clause.

Description	Cannot translate from WLQL to EJB QL. It is suggested that you use the following EJB QL: FROM abstract-schema-name AS X. Usage of EJB QL of this form will result in a Finder with no WHERE clause.
Cause	See the error message body.
Action	See the error message body.

BEA-013057

Error: \nProblem, in EJB QL the argument of OBJECT(field) in SELECT OBJECT(field) must be either a range variable identifier or a collection member identifier, either of which are defined in the query FROM clause as in 'SELECT OBJECT(e) FROM EmployeeBean AS e' or 'SELECT OBJECT(f) FROM EmployeeBean AS e, IN(e.friends)f'. 'field' is neither a range variable nor a collection member identifier. \n\nAction, review the EJB QL query and correct the SELECT clause.

Description	\nProblem, in EJB QL the argument of OBJECT(field) in SELECT OBJECT(field) must be either a range variable identifier or a collection member identifier, either of which are defined in the query FROM clause as in 'SELECT OBJECT(e) FROM EmployeeBean AS e' or 'SELECT OBJECT(f) FROM EmployeeBean AS e, IN(e.friends)f'. 'field' is neither a range variable nor a collection member identifier. \n\nAction, review the EJB QL query and correct the SELECT clause.
Cause	See the error message body.
Action	See the error message body.

BEA-013058(retired)

Error: In EJB QL, the argument of OBJECT(field) in SELECT OBJECT(field) must be a Range Variable that is mapped to an Abstract Schema Name ( EJBean ) that is declared in the FROM clause of the EJB QL Query. Found OBJECT argument 'field', which appears to be a cmp-field and not a Range Variable.

Description	In EJB QL, the argument of OBJECT(field) in SELECT OBJECT(field) must be a Range Variable that is mapped to an Abstract Schema Name (EJBean ) that is declared in the FROM clause of the EJB QL Query. Found OBJECT argument 'field', which appears to be a cmp-field and not a Range Variable.
Cause	See the error message body.
Action	See the error message body.

BEA-013059

Error: \nProblem, in EJB QL, the argument of OBJECT(field) 'field' must be an identifier that is declared as either a range variable identifier or a collection member identifier in the FROM clause of the query. 'field' is a path expression terminating in a cmp-field. It is not an identifier declared in the FROM clause. \n\nAction, rewrite the query paying attention to the SELECT clause.

Description	\nProblem, in EJB QL, the argument of OBJECT(field) 'field' must be an identifier that is declared as either a range variable identifier or a collection member identifier in the FROM clause of the query. 'field' is a path expression terminating in a cmp-field. It is not an identifier declared in the FROM clause. \n\nAction, rewrite the query paying attention to the SELECT clause.
Cause	See the error message body.
Action	See the error message body.

BEA-013060(retired)

Error: \nProblem, in EJB QL in the clause SELECT field, 'field' was expected to be a single_valued_path_expression. The single_valued_path_expression must consist of at least 2 elements separated by periods. 'field' contains only one element. \n\nAction, rewrite the SELECT clause of the query. See EJB2.0 Specification for more details.

Description	\nProblem, in EJB QL in the clause SELECT field, 'field' was expected to be a single_valued_path_expression. The single_valued_path_expression must consist of at least 2 elements separated by periods. 'field' contains only one element. \n\nAction, rewrite the SELECT clause of the query. See EJB2.0 Specification for more details.
Cause	See the error message body.
Action	See the error message body.

BEA-013061

Error: \nNote, in EJB QL, the argument of SELECT single_valued_path_expression cannot be an identification_variable. \n\t The compiler will assume that you meant to write the SELECT clause as SELECT OBJECT(field).

Description	\nNote, in EJB QL, the argument of SELECT single_valued_path_expression cannot be an identification_variable. \n\t The compiler will assume that you meant to write the SELECT clause as SELECT OBJECT(field).
Cause	See the error message body.
Action	See the error message body.

BEA-013062

Error: Sub-queries can only SELECT beans that have simple, non-compound Primary Keys. The bean specified by 'id' apparently has a compound key.

Description	Sub-queries can only SELECT beans that have simple, non-compound Primary Keys. The bean specified by 'id' apparently has a compound key.
Cause	See the error message body.
Action	See the error message body.

BEA-013063(retired)

Error: Left-hand argument to [NOT] MEMBER OF: 'Lhs' is a participant in a Many-To-Many Relationship. Left-hand argument to [NOT] MEMBER OF can only be single valued navigations. See the EJB 2.0 Final Spec '11.2.7.12 Collection Member Expressions'.

Description	Left-hand argument to [NOT] MEMBER OF: 'Lhs' is a participant in a Many-To-Many Relationship. Left-hand argument to [NOT] MEMBER OF can only be single valued navigations. See the EJB 2.0 Final Spec '11.2.7.12 Collection Member Expressions'.
Cause	See the error message body.
Action	See the error message body.

BEA-013064

Error: Cannot reliably generate a query that contains a NOT MEMBER OF clause, when the target of the query SELECT clause is not a subset of or equal to the left-hand side of NOT MEMBER OF: 'Lhs' and when the left-hand side of NOT MEMBER OF: 'Lhs' is not a subset of or equal to the SELECT clause target. One must be the subset of or equal to the other.

Description	Cannot reliably generate a query that contains a NOT MEMBER OF clause, when the target of the query SELECT clause is not a subset of or equal to the left-hand side of NOT MEMBER OF: 'Lhs' and when the left-hand side of NOT MEMBER OF: 'Lhs' is not a subset of or equal to the SELECT clause target. One must be the subset of or equal to the other.
Cause	See the error message body.
Action	See the error message body.

BEA-013065

Error: \nProblem, cannot perform Outer Join. Outer Join generation requires specification of a target database by including a database-type tag with the target database name in the weblogic-cmp-rdbms-jar.xml Deployment Descriptor file. \n\nAction, specify the target database by adding a database-type tag to the weblogic-cmp-rdbms-jar.xml Deployment Descriptor file.

Description	\nProblem, cannot perform Outer Join. Outer Join generation requires specification of a target database by including a database-type tag with the target database name in the weblogic-cmp-rdbms-jar.xml Deployment Descriptor file. \n\nAction, specify the target database by adding a database-type tag to the weblogic-cmp-rdbms-jar.xml Deployment Descriptor file.
Cause	See the error message body.
Action	See the error message body.

BEA-013066

Error: Cannot do Outer Join between Bean: 'bean1' and Bean: 'bean2' for Database 'database'. No database support for SQL Outer Join.

Description	Cannot do Outer Join between Bean: 'bean1' and Bean: 'bean2' for Database 'database'. No database support for SQL Outer Join.
Cause	See the error message body.
Action	See the error message body.

BEA-013067

Error: Cannot do Outer Join between Bean: 'bean1' and Bean: 'bean2' for Database 'database'. No database support for SQL Outer Join that involves more than two tables.

Description	Cannot do Outer Join between Bean: 'bean1' and Bean: 'bean2' for Database 'database'. No database support for SQL Outer Join that involves more than two tables.
Cause	See the error message body.
Action	See the error message body.

BEA-013068

Error: Cannot compile this EJB QL query, because it will require at least 'otjoinCount' SQL OUTER JOINs. However, the specified database: 'database' does not support this many OUTER JOINs per SQL Statement.

Description	Cannot compile this EJB QL query, because it will require at least 'otjoinCount' SQL OUTER JOINs. However, the specified database: 'database' does not support this many OUTER JOINs per SQL Statement.
Cause	See the error message body.
Action	See the error message body.

BEA-013069

Error: Error. Cannot perform this query on Oracle because a generated WHERE clause in the Query or one of its SubQueries would contain both an OR clause and an OUTER JOIN. Oracle DBMS will not execute a Query/SubQuery that contains an OR clause and an OUTER JOIN. The generated WHERE clause in question would have been: 'WHERE whereClause'

Description	Error. Cannot perform this query on Oracle because a generated WHERE clause in the Query or one of its SubQueries would contain both an OR clause and an OUTER JOIN. Oracle DBMS will not execute a Query/SubQuery that contains an OR clause and an OUTER JOIN. The generated WHERE clause in question would have been: 'WHERE whereClause'
Cause	See the error message body.
Action	See the error message body.

BEA-013070

Error: Error during deployment of EJB, 'ejbName'. The EJB references an application level cache, 'cacheName'. Applications that use this feature must be deployed using two-phase deployment. Make sure that 'TwoPhase=true' is specified for the application in config.xml if you are deploying the application statically.

Description	Error during deployment of EJB, 'ejbName'. The EJB references an application level cache, 'cacheName'. Applications that use this feature must be deployed using two-phase deployment. Make sure that 'TwoPhase=true' is specified for the application in config.xml if you are deploying the application statically.
Cause	See the error message body.
Action	See the error message body.

BEA-013071

Error: The finder method: 'failedMethod', defined in the home interface of EJB 'ejbName', does not have a corresponding finder element in the RDBMS deployment descriptor 'fileName'. Make sure the corresponding finder element exists and any declared finder-param elements contain the fully-qualified Java type name of the parameter.

Description	The finder method: 'failedMethod', defined in the home interface of EJB 'ejbName', does not have a corresponding finder element in the RDBMS deployment descriptor 'fileName'. Make sure the corresponding finder element exists and any declared finder-param elements contain the fully-qualified Java type name of the parameter.
Cause	See the error message body.
Action	See the error message body.

BEA-013072

Error: For relation: ejbName in weblogic-cmp-rdbms-jar.xml, join table 'joinTable' is defined. Join table for relationship other than many-to-many is not supported.

Description	For relation: ejbName in weblogic-cmp-rdbms-jar.xml, join table 'joinTable' is defined. Join table for relationship other than many-to-many is not supported.
Cause	See the error message body.
Action	See the error message body.

BEA-013073

Error: finder/ejbSelect 'finderName' has returned more than one value. We were expecting only ONE value. See EJB Spec 10.5.6.1, 10.5.7.1.

Description	finder/ejbSelect 'finderName' has returned more than one value. We were expecting only ONE value. See EJB Spec 10.5.6.1, 10.5.7.1.
Cause	See the error message body.
Action	See the error message body.

BEA-013074

Error: Duplicate AS definition of 'Id' in FROM clause.

Description	Duplicate AS definition of 'Id' in FROM clause.
Cause	See the error message body.
Action	See the error message body.

BEA-013075

Error: \nProblem, the range variable identifier 'Id' has been declared more than once in the query. A range variable identifier value can only be declared once in a query, including any subqueries. \n\nAction, choose an alternative value for the duplicate range variable identifier currently declared as 'Id'.

Description	\nProblem, the range variable identifier 'Id' has been declared more than once in the query. A range variable identifier value can only be declared once in a query, including any subqueries. \n\nAction, choose an alternative value for the duplicate range variable identifier currently declared as 'Id'.
Cause	See the error message body.
Action	See the error message body.

BEA-013076

Error: Error, could not find Range Variable, as declared in FROM clause, for EJBean: 'ejbName' with AbstractSchemaName: 'abstractSchemaName'.

Description	Error, could not find Range Variable, as declared in FROM clause, for EJBean: 'ejbName' with AbstractSchemaName: 'abstractSchemaName'.
Cause	See the error message body.
Action	See the error message body.

BEA-013077

Error: \nProblem, the collection member identifier 'Id' has been declared more than once in the query. A collection member identifier value can only be declared once in a query, including any subqueries. \n\nAction, choose an alternative value for the duplicate collection member identifier currently declared as 'Id'.

Description	\nProblem, the collection member identifier 'Id' has been declared more than once in the query. A collection member identifier value can only be declared once in a query, including any subqueries. \n\nAction, choose an alternative value for the duplicate collection member identifier currently declared as 'Id'.
Cause	See the error message body.
Action	See the error message body.

BEA-013078

Error: Correlation variable 'id' is defined more than once.

Description	Correlation variable 'id' is defined more than once.
Cause	See the error message body.
Action	See the error message body.

BEA-013079

Error: The pathExpression/Identifier 'id' contains a root: 'asID' that is not defined in an AS declaration in the FROM clause.

Description	The pathExpression/Identifier 'id' contains a root: 'asID' that is not defined in an AS declaration in the FROM clause.
Cause	See the error message body.
Action	See the error message body.

BEA-013080

Error: \nProblem, the path expression/Identifier 'pathExpression' starts with an identifier: 'identificationVar'. The identifier 'identificationVar', which can be either a range variable identifier or a collection member identifier, is required to be declared in the FROM clause of its query or in the FROM clause of a parent query. 'identificationVar' is not defined in the FROM clause of either its query or in any parent query. \n\nAction, rewrite the query paying attention to the usage of 'pathExpression'.

Description	\nProblem, the path expression/Identifier 'pathExpression' starts with an identifier: 'identificationVar'. The identifier 'identificationVar', which can be either a range variable identifier or a collection member identifier, is required to be declared in the FROM clause of its query or in the FROM clause of a parent query. 'identificationVar' is not defined in the FROM clause of either its query or in any parent query. \n\nAction, rewrite the query paying attention to the usage of 'pathExpression'.
Cause	See the error message body.
Action	See the error message body.

BEA-013081

Error: This EJB-QL query will produce an empty result if any of these underlying DBMS tables are empty: list. For more details regarding this behavior, see the EJB-QL section of the WebLogic Server documentation.

Description	See the error message body.
Cause	See the error message body.
Action	See the error message body.

BEA-013082

Error: The argument to IS [NOT] NULL must be a single valued path expression or a variable.\n. For example, a proper argument might be: \n 'WHERE ?1 IS NULL' or \n 'WHERE employee.manager IS NULL' where an employee can only have one manager.\n\n. Query found an IS [NOT] NULL argument 'arg' that is neither a single valued path expression or a variable.

Description	See the error message body.
Cause	See the error message body.
Action	Re-evaluate the query and rewrite it.

BEA-013083(retired)

Error: The argument to IS [NOT] NULL Must be a single valued path expression.\n for example a proper argument might be: \n 'WHERE employee.manager IS NULL' where an employee can only have one manager.\n\n We found an IS [NOT] NULL argument 'arg' which is not a single valued path expression.

Description	See the error message body.
Cause	See the error message body.
Action	Re-evaluate the query and rewrite it.

BEA-013084

Error: Exception during compilation: Finder method 'finderName' of EJB 'ejbName' contains a GROUP BY clause and use-select-for-update is set to true for this EJB. The two are not compatible.

Description	see message body
Cause	see message body
Action	re-evaluate the query and rewrite it or do not set use-select-for-update to true for this entity bean.

BEA-013085

Error: All ejbSelect methods that select multiple fields must have a return type of java.sql.ResultSet. This method has a return type of returnClass. You must either modify the EJB QL for the query to select a single value or change the return type of the query to be java.sql.ResultSet.

Description	Query methods that select multiple fields must have a return type of java.sql.ResultSet. The method selects multiple fields but does not return a ResultSet.
Cause	See the error message body.
Action	See the error message body.

BEA-013086

Error: The LIKE operator is missing an argument.\n The syntax for LIKE is single_valued_path_expression [NOT] LIKE pattern_value [ESCAPE escape-character] \n The single_valued_path_expression AND pattern_value are required.\n

Description	see message body
Cause	See the error message body.
Action	re-examine your query and rewrite the LIKE operator and it's operands.

BEA-013087

Warning: The first character 'badboy' in the identifier 'identifier' is not a valid first character to use in an EJB QL identifier. \n According to the EJB QL specification, the first character must return true when used as an argument to \n java.lang.Character.isJavaIdentifierStart(char c).

Description	see message body
Cause	See the error message body.
Action	re-examine your query and consider renaming this identifier.

BEA-013088

Warning: The character 'badboy' in the identifier 'identifier' is not a valid character to use in an EJB QL identifier. \n According to the EJB QL specification, any character after the first character in the identifier must return true \n when used as an argument to java.lang.Character.isJavaIdentifierPart(char c).

Description	see message body
Cause	See the error message body.
Action	re-examine your query and consider renaming this identifier.

BEA-013089

Warning: The character 'badboy' in the identifier 'identifier' is not a valid character to use in an EJB QL identifier. \n We are allowing the use of this character for backwards compatibility with earlier releases of WebLogic Server.

Description	see message body
Cause	See the error message body.
Action	re-examine your query and consider renaming this identifier.

BEA-013090

Error: Error processing query for EJB 'ejbName': The UPPER and LOWER operators can only be used in the SELECT clause on path expressions ending in a CMP field of type String or Character. The variable 'selectTarget' is not a path expression.

Description	see message body
Cause	See the error message body.
Action	Re-examine your query and ensure the usage of the UPPER and LOWER operators is correct.

BEA-013091

Error: Error processing query for EJB 'ejbName': For all aggregate functions except COUNT, the path expression that is the argument to the aggregate function must terminate in a cmp-field. The expression 'selectTarget' does not terminate in a cmp-field.

Description	see message body
Cause	See the error message body.
Action	Re-examine your query and ensure the usage of the aggregate function is correct.

BEA-013092

Error: NOTE: The original EJB QL Query has been rewritten for the following reasons: 'reasons'\n\n Any compilation errors refer to the compilation of the rewritten EJB QL query.\n\n The original EJB QL Query was:

Description	see message body
Cause	See the error message body.
Action	Re-examine the errors in the rewritten query and correct the corresponding area(s) of the original query.

BEA-013093

Error: ''NOT'' Expressions have been factored out and removed to preserve any generated SQL joins.

Description	see message body
Cause	See the error message body.
Action	None.

BEA-013094

Warning: The SELECT clause of this query contains an identifier 'identifier' that ends in a cmr-field. The EJB 2.1 specification section 11.2.7.1 requires that any related null objects belonging to the set corresponding to this cmr-field must be returned by this query however the database that will be used to execute this query does not sufficiently support SQL outer joins, therefore this query will not return any null objects that might otherwise be returned.

Description	see message body
Cause	See the warning message body.
Action	None.

BEA-013095

Error: Invalid relationship-caching name. No relationship-caching with the name 'cachingName' was declared for this EJB in the RDBMS deployment descriptor.

Description	Invalid relationship-caching name. No relationship-caching with the name 'cachingName' was declared for this EJB in the RDBMS deployment descriptor.
Cause	See error message body.
Action	Declare a valid relationship-caching name for the Dynamic Query

BEA-013096

Error: \nProblem, in EJB QL in the clause 'SELECT fieldName'. The expression 'fieldName' was expected to either contain an identification variable qualified by the OBJECT operator or a single_valued_path_expression. The single_valued_path_expression must consist of at least 2 elements separated by periods. \n\nAction, rewrite the SELECT clause of the query. See EJB2.x Specification for more details.

Description	See error message body.
Cause	See error message body.
Action	Rewrite the SELECT clause of the query.

BEA-014000

Error: Problem, encountered illegal value for transaction-isolation 'readValue' \n\nAction. Specify a legal value: TransactionSerializable | TransactionReadCommitted | TransactionReadCommittedForUpdate | TransactionReadCommittedForUpdateNoWait | TransactionReadUncommitted | TransactionRepeatableRead

Description	Problem, encountered illegal value for transaction-isolation 'readValue' \n\nAction. Specify a legal value: TransactionSerializable \| TransactionReadCommitted \| TransactionReadCommittedForUpdate \| TransactionReadCommittedForUpdateNoWait \| TransactionReadUncommitted \| TransactionRepeatableRead
Cause	See the error message body.
Action	See the error message body.

BEA-014001

Error: Warning: RDBMS descriptor fileName contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console. The isolation-level settings should be moved to the weblogic-ejb-jar.xml descriptor.

Description	Warning: RDBMS descriptor fileName contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console. The isolation-level settings should be moved to the weblogic-ejb-jar.xml descriptor.
Cause	See the error message body.
Action	See the error message body.

BEA-014002(retired)

Error: Duplicate relation name 'name' found while processing ejb-jar deployment descriptor. The ejb-relation-name values must be unique.

Description	Duplicate relation name 'name' found while processing ejb-jar deployment descriptor. The ejb-relation-name values must be unique.
Cause	See the error message body.
Action	See the error message body.

BEA-014003

Warning: Warning: EJB ejbName uses optimistic concurrency and contains a finder or select method, methodSig, for which include-updates is true. This combination of features does not work properly with database database.

Description	Warning: EJB ejbName uses optimistic concurrency and contains a finder or select method, methodSig, for which include-updates is true. This combination of features does not work properly with database database.
Cause	Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency doesnt hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.
Action	Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.

BEA-014004

Warning: Warning: In EJB ejbName, is set to 'genKeyType'. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.

Description	Warning: In EJB ejbName, is set to 'genKeyType'. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.
Cause	Database limitations.
Action	Turn off automatic-key-generation in order to use Batch Operations.

BEA-014005

Warning: The configured dispatch policy "dispatchPolicy" for message driven bean (MDB) "ejbName" will be ignored: the MDB is not running in a WebLogic thread.

Description	The thread pool for an MDB is configured using the optional dispatch-policy attribute in the MDBs WebLogic descriptor file.
Cause	The queue MDB is driven asynchronously by a non WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.
Action	To disable this warning, remove the "dispatch-policy" setting from the MDBs WebLogic descriptor file.

BEA-014006

Warning: The message driven bean (MDB) named "mdbName" has a dispatch policy "dispatchPolicy" that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.

Description	The execute thread queue pool for an MDB is configurable using the WebLogic descriptor dispatch-policy attribute. If the dispatch policy is not specified or refers to an unknown thread execute queue, the MDB uses the default thread execute queue.
Cause	The message driven bean (MDB) named "mdbName" has a dispatch policy "dispatchPolicy" that refers to an unknown execute queue thread pool.
Action	Create an execute thread queue pool for the server named "dispatchPolicy", or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.

BEA-014007

Warning: The bean named "ejbName" contains Blob and/or Clob fields and uses Optimistic Concurrency \n but no "version" or "timestamp" column has been specified. \n this may result in corruption of Blob and/or Clob data.

Description	see message body.
Cause	see message body.
Action	Specify "version" or "timestamp" in the element \n and specify the name of the or column in the element.

BEA-014008

Warning: In ejb "ejbName", finderName references an SqlShape element "shapeName" that is not defined. The list of SqlShape elements that are defined for this EJB is: candidates.

Description	see message body.
Cause	see message body.
Action	Use an existing SqlShape or create the SqlShape that you wish to use.

BEA-014009

Info: The MessageDrivenBean "mdbName" of application "appName" will now be suspended, as it listens to global JMS destination "destination" and a new application version "newVersion" is being redeployed.

Description	see message body.
Cause	see message body.
Action	No action required.

BEA-014010

Warning: The MessageDrivenBean "mdbName" of application "appName" will now be suspended, as it listens to global JMS topic "destination" and a new application version "newVersion" is being redeployed. Please also note that the current MessageDrivenBean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the MessageDrivenBean is suspended may not be received by the new application version. To ensure that the new application version will receive all messages published while the MessageDrivenBean was suspended, please set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.

Description	see message body.
Cause	see message body.
Action	To ensure that the new application version will receive all messages published while the MessageDrivenBean was suspended, please set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.

BEA-014011

Warning: Warning: EJB ejbName, uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.

Description	see message body.
Cause	Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.
Action	Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

BEA-014012

Warning: Warning: EJB ejbName, uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.

Description	see message body.
Cause	Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.
Action	Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.

BEA-014013

Warning: Warning: EJB ejbName, does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant for these of these concurrency strategies only.

Description	see message body.
Cause	When an EJB using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.
Action	Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.

BEA-014014

Warning: The message driven bean (MDB) named "mdbName" has a dispatch policy "dispatchPolicy" that refers to an unknown work manager. The default work manager will be used instead.

Description	The work manager for an MDB is configurable using the WebLogic descriptor dispatch-policy attribute. If the dispatch policy is not specified or refers to an unknown work manager, the MDB uses the default work manager.
Cause	The message driven bean (MDB) named "mdbName" has a dispatch policy "dispatchPolicy" that refers to an unknown work manager.
Action	Create an work manager for the server named "dispatchPolicy", or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.

BEA-014015(retired)

Warning: Warning: EJB ejbName, has the remote-client-timeout set to timeout secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.

Description	See message body.
Cause	See message body.
Action	See message body.

BEA-014016

Warning: Warning: EJB ejbName, uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is readonly, select-for-update is unnecessary.

Description	see message body.
Cause	ReadOnly beans cannot be updated. Therefore, use-select-for-update is unnecessary.
Action	Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

BEA-014017

Warning: Warning: EJB ejbName, uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.

Description	see message body.
Cause	Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary as the bean is locked by the container.
Action	Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

BEA-014018

Warning: Warning: EJB ejbName, uses verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since, this bean does not use optimistic concurrency, this element will be ignored.

Description	see message body.
Cause	verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
Action	Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.

BEA-014019

Warning: Warning: EJB ejbName, uses verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since, this bean does not use optimistic concurrency, this element will be ignored.

Description	see message body.
Cause	verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
Action	Remove verify-rows element in the RDBMS deployment descriptor to avoid this warning message.

BEA-014020

Warning: Warning: EJB ejbName, uses optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since, this bean does not use optimistic concurrency, this element will be ignored.

Description	see message body.
Cause	optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.
Action	Remove optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.

BEA-014021

Info: The EJB 'ejbName' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:

Description

see message body.

BEA-014022

Info: ******** businessIntfName is bound with JNDI name:jndiName ********

Description

see message body.

BEA-011223

Info: Cannot invoke stateful callback on beanType

Description

see message body.

BEA-011224

Info: Unable to bind the interface interfaceName to name. Another EJB has already bound an interface to that name."

Description

see message body.

BEA-011225

Info: Unable to bind the interface interfaceName to name. This EJB has declared another interface already bound to that name

Description

see message body.

BEA-011226

Info: Error during 'name'. Couldn't get connection: \n exception \ntrace

Description

see message body.

BEA-011227

Info: Error during finder 'name'. Exception while preparing query: 'query'\n exception \ntrace

Description

see message body.

BEA-011228(retired)

Info: Couldn't get connection: \nexception\ntrace

Description

see message body.

BEA-011229(retired)

Info: Error constructing query: \nexception\ntrace

Description

see message body.

BEA-011230(retired)

Info: Error calling getDatabaseProductName: \nexception\ntrace

Description

see message body.

BEA-011231(retired)

Info: Error calling getDatabaseProductVersion: \nexception\ntrace

Description

see message body.

BEA-011232

Info: Error during finder 'name'. Exception while setting parameters for query 'query'\nexception\ntrace

Description

see message body.

BEA-011233

Info: Error during finder 'name'. Exception while executing query 'exception'\ntrace

Description

see message body.

BEA-011234

Info: Could not find an EJB with a field that is mapped to table 'table'and column 'column'. The SQL query is 'query'. Try using an SqlShape annotation to describe the query results or check that the SqlShape annotation in use is correct.

Description

see message body.

BEA-011235

Info: Error in 'name', could not map relationship 'relation' role 'role' to an EJB populated by the query 'query'. EJBs populated by this query are: candidates

Description

see message body.

BEA-011236

Info: Error executing finder 'finder: SqlShape 'sqlshape' contains size columns, but the result set returned by JDBC contains count columns. The number of columns in the SqlShape and the JDBC result set must match.

Description

see message body.

BEA-011237

Info: A stored procedure or function is used by 'name', but no SqlShape is specified.

Description

see message body.

BEA-011238

Info: Error in 'name'. SQL query 'query' does not select column values for all primary key fields of bean 'name'. No columns were selected for the following fields: field

Description

see message body.

BEA-011239

Info: Query-caching is not supported for read-write beans

Description

see message body.

BEA-011240

Info: Error obtaining nativeQuery: msg, excep

Description

see message body.

BEA-011241

Info: Attempt to do executeQuery on query 'query', using a non-WebLogic EntityManager

Description

see message body.

BEA-011242

Info: Internal Error: Extended Persistence Context has been closed!!!!

Description

see message body.

BEA-011243

Info: attempt at illegal state transaction from oldState to state

Description

see message body.

BEA-011244

Info: Illegal call to EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces

Description

see message body.

BEA-011245

Info: The EJB name is not a EJB3.0 bean!

Description

see message body.

BEA-011246

Info: The EJB bean doesn't declare a local home interface!

Description

see message body.

BEA-011247

Info: The EJB bean does not implement the business interface interface

Description

see message body.

BEA-011248

Info: the bean has not been invoked through a business interface .

Description

see message body.

BEA-011249

Info: It is illegal to invoke UserTransaction methods in ejbCreate or PostConstruct method of message driven bean.

Description

see message body.

BEA-011250

Info: It is illegal to invoke UserTransaction methods in ejbRemove or PreDestroy method of message driven bean.

Description

see message body.

BEA-011251

Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of message driven bean.

Description

see message body.

BEA-011252

Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of stateful session bean.

Description

see message body.

BEA-011253

Info: It is illegal to invoke UserTransaction methods in ejbCreate or PostConstruct method of stateless session bean.

Description

see message body.

BEA-011254

Info: It is illegal to invoke UserTransaction methods in ejbRemove or PreDestroy method of stateless session bean.

Description

see message body.

BEA-011255

Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of stateless session bean.

Description

see message body.

BEA-011256

Info: Single expiration timers cannot be cancelled from within ejbTimeout

Description

see message body.

BEA-011257

Info: It''s illegal to invoke Timer methods in ejbRemove or PreDestroy method from session bean or MDB

Description

see message body.

BEA-011258

Info: It''s illegal to invoke Timer methods in ejbActivate or PostActivate method

Description

see message body.

BEA-011259

Info: It''s illegal to invoke Timer methods in ejbPassivate or PrePassivate method

Description

see message body.

BEA-011260

Info: it''s illegal to invoke Timer methods during dependency injection

Description

see message body.

BEA-011261

Info: Invocation timed out. Timer is busy.

Description

see message body.

BEA-011262

Info: Error cancelling timer.

Description

see message body.

BEA-011263

Info: EjbJarBean not set yet

Description

see message body.

BEA-011264

Info: Method method is marked TX_NEVER, but was called within a transaction.

Description

see message body.

BEA-011265

Info: Unexpected exception in afterDelivery(): exception

Description

see message body.

BEA-011266

Info: Attempt to execute getDatabaseProductName using a non-WebLogic EntityManager.

Description

see message body.

BEA-011267

Info: Error calling getDatabaseProductName: stack

Description

see message body.

BEA-011268

Info: Attempt to execute nativeQuery on query 'query', using a non-WebLogic EntityManager.

Description

see message body.

BEA-011269

Info: Error obtaining nativeQuery: stack

Description

see message body.

BEA-011270

Info: Error preparing query: stack

Description

see message body.

BEA-011271(retired)

Info: encounter a remote exception, the nested exception is:

Description

see message body.

BEA-011272(retired)

Info: Error adding handler chain: errorMsgs

Description

see message body.

BEA-011273(retired)

Info: @EJB annotation doesn''t have beanInterface set

Description

see message body.

BEA-011274(retired)

Info: A class level type annotation on class class does not have the name attribute set.

Description

see message body.

BEA-011275(retired)

Info: A class level Resource annotation on class class does not have the type attribute set

Description

see message body.

BEA-011276

Info: Illegal attempt to make a reentrant call to a stateful session bean: name

Description

see message body.

BEA-011277

Info: Illegal attempt to make a reentrant call to a stateful session bean from home: name

Description

see message body.

BEA-015001

Info: Unable to link class class in Jar jar : exception

Description

see message body.

BEA-015002

Info: Unable to load class class in Jar jar : exception

Description

see message body.

BEA-015003

Info: Unable to create virual Jar jar : exception

Description

see message body.

BEA-015004

Info: The super class superClass of session bean class class is also a session bean class.

Description

see message body.

BEA-015005

Info: session type are not set in deployment descriptor or annotation for session bean class

Description

see message body.

BEA-015006(retired)

Info: The session bean name does not have a client view specified. Since the bean class class implements multiple interfaces, you must indicate which of these interfaces are local or remote business interfaces by means of the Local or Remote annotation or in the deployment descriptor.

Description

see message body.

BEA-015007

Info: No ejbCreate method was found for init method: method in bean class

Description

see message body.

BEA-015008

Info: No matching create method for @Init method: method in bean class

Description

see message body.

BEA-015009

Info: Couldn't load interceptor class class: exceptionMsg

Description

see message body.

BEA-015010

Info: In bean class , there are multiple method permission annotations for method: method ,which is illegal.

Description

see message body.

BEA-015011

Info: There are multiple method permission annotations for class: class ,which is illegal.

Description

see message body.

BEA-015012

Info: Unable to load interface class class: exception

Description

see message body.

BEA-015013

Info: Bean class class doesn't implement interface method: method.

Description

see message body.

BEA-015014

Info: ServiceEndpoint class:class was specified but can not be found.

Description

see message body.

BEA-015015

Info: The super class superClass of message-driven bean class class is also a message-driven bean class.

Description

see message body.

BEA-015016

Info: MDB class implements multiple interfaces and no messageListenerInterface was specified in the @MessageDriven annotation

Description

see message body.

BEA-015017

Info: In bean class class, @EJB annotation is at class level, so beanInterface must be explicitly specified

Description

see message body.

BEA-015018

Info: In interceptor class class , @EJB annotation is at class level, so beanInterface must be explicitly specified

Description

see message body.

BEA-015019

Info: If a session bean instance is participating in a transaction, it is an error for a client to invoke a method on the session object such that the transaction attribute specified in the bean''s metadata annotations and/or the deployment descriptor would cause the container to execute the method in a different transaction context or in an unspecified transaction context. You may also consider setting the option in your weblogic-ejb-jar.xml. When this tag is set, the concurrent call waits for the first method call to complete.

Description

see message body.

BEA-015020

Error: Cannot specify @JNDIName on both the remote interface and the implementation class. Class: clsName; interface: ifaceName.

Description	Cannot specify @JNDIName on both the remote interface and the implementation class. Class: clsName; interface: ifaceName.
Cause	Cannot specify @JNDIName on both the remote interface and the implementation class. Class: clsName; interface: ifaceName.
Action	Remove @JNDIName from either clsName or ifaceName.

BEA-015021

Error: Cannot specify @JNDIName on the implementation for a class with multiple remote interfaces. Class: clsName; interfaces: ifaces.

Description	Cannot specify @JNDIName on the implementation for a class with multiple remote interfaces. Class: clsName; interfaces: ifaces.
Cause	Cannot specify @JNDIName on the implementation for a class with multiple remote interfaces. Class: clsName; interfaces: ifaces.
Action	Remove @JNDIName from clsName.

BEA-015022

Error: annoType is not valid in this context. Bean class: clsName.

Description	annoType is not valid in this context. Bean class: clsName.
Cause	annoType is not valid in this context. Bean class: clsName.
Action	Remove annoType from the invalid location.

BEA-015023

Error: annoType is not valid in this context. Bean method: clsName.methName.

Description	annoType is not valid in this context. Bean method: clsName.methName.
Cause	annoType is not valid in this context. Bean method: clsName.methName.
Action	Remove annoType annotation from invalid location.

BEA-015024

Error: Couldn't specify @JNDIName on local business interface: interface of Bean:beanName.

Description	Couldn't specify @JNDIName on local business interface: interface of Bean:beanName.
Cause	Couldn't specify @JNDIName on local business interface: interface of Bean:beanName.
Action	Remove annotation from local business interfacec.

BEA-015025

Error: Unable to load a class specified in your ejb-jar.xml: msg.

Description	Unable to load a class specified in your ejb-jar.xml: msg.
Cause	Unable to load a class specified in your ejb-jar.xml: msg.
Action	Check ejb-jar.xml in ejb jar file.

BEA-015026

Error: Reference name 'name' of @annotationName annotation on class className is not unique.

Description	Reference name 'name' of @annotationName annotation on class className is not unique.
Cause	Reference name 'name' of @annotationName annotation on class className is not unique.
Action	Change the reference name 'name' of @annotationName annotation on class className.

BEA-015027

Error: The Message-Driven EJB is transactional but JMS connection factory referenced by the JNDI name: name is not a JMS XA connection factory.

Description	The Message-Driven EJB is transactional but JMS connection factory referenced by the JNDI name: name is not a JMS XA connection factory. If EJB is using transactional context then connection factory also need to provide XA transactional support.
Cause	See error message body.
Action	See error message body.

BEA-015028

Error: The EJB name contains an illegal value for the activation config property 'DistributedDestinationConnection'. The specified value is propertyValue but the legal value: EveryMemeber | LocalOnly

Description	The EJB name contains an illegal value for the activation config property 'DistributedDestinationConnection'. The specified value is propertyValue but the legal value: EveryMemeber \| LocalOnly
Cause	See error message body.
Action	See error message body.

BEA-015029

Error: The EJB name contains an illegal value for the activation config property 'TopicMessagesDistributionMode'. The specified value is propertyValue but the legal values are: Compatibility | One-Copy-Per-Server | One-Copy-Per-Application

Description	The EJB name contains an illegal value for the activation config property 'TopicMessagesDistributionMode'. The specified value is propertyValue but the legal values are: Compatibility \| One-Copy-Per-Server \| One-Copy-Per-Application
Cause	See error message body.
Action	See error message body.

BEA-015030

Error: The EJB 'name' has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topic works with 'Compatibility', 'One-Copy-Per-Server' or 'One-Copy-Per-Application'; but partitioned distributed topic only works with 'One-Copy-Per-Server' or 'One-Copy-Per-Application'. The EJB is configured to 'partitioned distributed topic' and 'Compatibility'.

Description	The EJB 'name' has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topic works with 'Compatibility', 'One-Copy-Per-Server' or 'One-Copy-Per-Application'; but partitioned distributed topic only works with 'One-Copy-Per-Server' or 'One-Copy-Per-Application'. The EJB is configured to 'partitioned distributed topic' and 'Compatibility'.
Cause	See error message body.
Action	See error message body.

BEA-015031

Warning: The EJB name has a 'distributedDestinationConnection' configured but the EJB is configured to connect to a remote cluster. Since the 'distributedDestinationConnection' configuration is only valid in a local cluster, the setting will be ignored.

Description	The EJB name has a 'distributedDestinationConnection' configured but the EJB is configured to connect to a remote cluster. Since the 'distributedDestinationConnection' configuration is only valid in a local cluster, the setting will be ignored.
Cause	See error message body.
Action	See error message body.

BEA-015032

Error: The EJB name is configured with the activation config property 'topicMessagesDistributionMode' but the EJB is configured to connect to a JMS Queue. The 'topicMessagesDistributionMode' is only valid for JMS Topic destinations.

Description	The EJB name is configured with the activation config property 'topicMessagesDistributionMode' but the EJB is configured to connect to a JMS Queue. The 'topicMessagesDistributionMode' is only valid for JMS Topic destinations.
Cause	See error message body.
Action	See error message body.

BEA-015033

Error: The EJB name has an invalid value configured for the activation config property 'property'.Only WebLogic JMS server 10.3.4 or later versions support the values 'One-Copy-Per-Server' or 'One-Copy-Per-Application'. For prior to 10.3.4.0 Weblogic JMS server or other non Weblgoic JMS vendors only the 'Compatibility' value is supported.

Description	The EJB name has an invalid value configured for the activation config property 'property'.Only WebLogic JMS server 10.3.4 or later versions support the values 'One-Copy-Per-Server' or 'One-Copy-Per-Application'. For prior to 10.3.4.0 Weblogic JMS server or other non Weblgoic JMS vendors only the 'Compatibility' value is supported.
Cause	See error message body.
Action	See error message body.

BEA-015034

Error: this destinaiton destinationName is remote replicated distribution topic which does not support durable subscriptions when the MDB ejbName works on 'Compatibility' mode

Description	this destinaiton destinationName is remote replicated distribution topic which does not support durable subscriptions when the MDB ejbName works on 'Compatibility' mode
Cause	See error message body.
Action	See error message body.

BEA-015035

Warning: The EJB name is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.

Description	The EJB name is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.
Cause	See error message body.
Action	See error message body.

BEA-015036

Warning: In the EJB name, the value for the activation config property 'propertyName' will be ignored since it is overridden with the value 'properValue';

Description	In the EJB name, the value for the activation config property 'propertyName' will be ignored since it is overridden with the value 'properValue';
Cause	See error message body.
Action	See error message body.

BEA-015037

Warning: In EJB ejbName, the throws clause for method methodSigString in the bean class contains exceptions that are NOT in the throws clause of the corresponding interfaceType interface method.

Description	In EJB ejbName, the throws clause for method methodSigString in the bean class contains exceptions that are NOT in the throws clause of the corresponding interfaceType interface method.
Cause	See error message body.
Action	See error message body.

BEA-015038

Info: Problems definitively matching up the interface method method with a method in the bean class. Please modify your bean class to implement the interface intf

Description

see message body.

BEA-015039

Error: Can not start an inactive message driven bean name. A redployment may be needed.

Description	Can not start an inactive message driven bean name. A redployment may be needed.
Cause	See error message body.
Action	See error message body.

BEA-015040

Info: The message driven bean name is inactive now.

Description	The message driven bean name is inactive now.
Cause	See error message body.
Action	See error message body.

BEA-015041

Info: The message driven bean name is active now.

Description	The message driven bean name is active now.
Cause	See error message body.
Action	See error message body.