Breadcrumb();
> Message Index (by Number) (by Subsystem) > EJB Subsystem Messages
EJB Subsystem Messages
|
The EJB1.0 catalog contains messages in the range
BEA010000 - BEA019999. Messages in this catalog are part of the
Info: Exception occurred during ejbActivate: excep
Description
Cause
Action
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
Cause
Action
Error: An error occurred while undeploying:deploymentName.
Description
Cause
Action
Error: Exception occurred while loading _WL_TIMESTAMP FILE.
Description
Cause
Action
Warning: The EJB deployment named: deploymentName was compiled by a different version of WebLogic Server.
Description
Cause
Action
Warning: Error occurred while reading WebLogic Server-generated files in deployment: deploymentName. Exception is: ioExcep.
Description
Action
Error: Error occurred while saving ejb deployment timestamps. ioExcep
Description
Cause
Action
Info: License validation passed for ejbVersion.
Description
Info: EJB Deploying file: beanFile
Description
Info: EJB Deployed EJB with JNDI name jndiName.
Description
Info: Exception looking up current transaction:\n stackTrace
Description
Info: Exception looking up current transaction:\n stackTrace
Description
Info: Exception looking up current transaction:\n stackTrace
Description
Warning: EJB "EJBName" referenced an undeclared security role "roleName".
Description
Notice: Error occurred while attempting to rollback transaction: excep
Description
Cause
Action
Notice: Error occurred while marking transaction for rollback: exp.
Description
Cause
Action
Notice: Exception occurred while marking transaction for rollback: exp.
Description
Cause
Action
Notice: Exception occurred during rollback of transaction transaction: stackTrace.
Description
Cause
Action
Notice: Error occurred while resuming caller transaction: excep
Description
Cause
Action
Warning: Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.
Description
Cause
Action
Error: EJB-20 - MessageDriven - Could not start the JMS connection: excep
Description
Cause
Action
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
Cause
Action
Error: Error occurred in ejbPassivate: stackTrace.
Description
Cause
Action
Error: Diskswap - error in setup for StatefulEJBCache:\n stackTrace.
Description
Cause
Action
Error: Error occurred during passivation: stackTrace
Description
Cause
Action
Error: Exception occurred during rollback of transaction transaction: stackTrace
Description
Cause
Action
Error: Exception occurred during commit of transaction transaction: stackTrace.
Description
Cause
Action
Info: Exception occurred during rollback of transaction transaction: stackTrace.
Description
Cause
Action
Info: Exception occurred during commit of transaction transaction: stackTrace.
Description
Cause
Action
Info: Exception occurred during commit of transaction transaction: stackTrace.
Description
Cause
Action
Info: Ignoring exception that occurred during roll back a transaction during undeployment of homeJNDIName.
Description
Cause
Action
Info: EJB Exception in method: MethodName: throwable.
Description
Action
Info: Exception during ejbActivate(): stackTrace
Description
Action
Info: Exception from ejbLoad: throwable
Description
Action
Info: Exception from ejbStore: throwable.
Description
Action
Info: EJB Exception occurred during invocation from home: ejbHome and primary key: primKey threw exception: throwable
Description
Action
Info: Exception from ejbStore: throwable.
Description
Action
Info: Exception from ejbLoad: throwable.
Description
Action
Info: Exception from __WL_superEjbLoad: throwable.
Description
Action
Info: Exception in ejbStore: throwable.
Description
Action
Info: Exception in ejbStore: throwable.
Description
Action
Info: ERROR creating secondary: namingException.
Description
Action
Info: ERROR becoming primary server: namingException.
Description
Action
Info: Exception in ejbActivate: stackTrace.
Description
Action
Info: Exception trying to resume transaction: excep.
Description
Action
Info: Exception in afterBegin: stackTrace.
Description
Action
Info: Exception in beforeCompletion: stackTrace.
Description
Action
Info: Exception during setRollbackOnly: excep.
Description
Action
Info: Exception in afterCompletion: stackTrace.
Description
Action
Info: EJB Exception in method: methodName: throwable.
Description
Action
Info: A stateless session bean with bean-managed transactions must commit or rollback a transaction before the business method completes.
Description
Action
Info: EJB Exception occurred during invocation from home: ejbHome threw exception: throwable
Description
Info: An exception occurred while creating the freepool.
Description
Warning: Warning: disregarding principal "prinName"\ mapped to\nrole "roleName" because it is not found in realm "\realmName"\
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Could not find a license for EJB 3.0. Please contact BEA to get a license.
Description
Cause
Action
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
Error: An Error occurred while attempting to invalidate the target Read-Only Entity EJB: ejbName. The error was:\nmsg
Description
Cause
Action
Info: The Message-Driven EJB: ejbName has connected/reconnected to the JMS destination: destName.
Description
Cause
Action
Warning: The Message-Driven EJB: ejbName is unable to connect to the JMS destination: destName. The Error was:\nerrorMsg
Description
Cause
Action
Warning: The Message-Driven EJB: ejbName encountered an error while closing its connection to the JMS destination. The error was:\n errorMsg
Description
Cause
Action
Warning: The EJB: ejbName had an
Description
Cause
Action
Info: The EJB: ejbName threw an Exception during undeployment or redeployment of its application. This exception is ignored. The exception was:\n errorMsg.
Description
Warning: MessageDrivenBean threw an Exception in onMessage(). The exception was:\n e.
Description
Cause
Action
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
Info: Exception during ejbRemove: excep
Description
Error: EJB-20 - MessageDriven - Could not recover JMS session: excep
Description
Cause
Action
Error: Error occurred while preparing EJB Module : moduleName.
Description
Cause
Action
Error: Error occurred while activating EJB Module : moduleName.
Description
Cause
Action
Error: Error occurred while performing Pop of Caller Principal: excep.
Description
Cause
Action
Error: Error occurred while starting EJB Module : moduleName\nException is : excep
Description
Cause
Action
Warning: Unable to add the interfaceName interface "className" and any dependent classes to the client-jar since it was loaded from the Classpath.
Description
Cause
Action
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
Cause
Action
Info: Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.
Description
Info: Client-jar "jarName" created.
Description
Error: Error committing a JMS transaction for the message-driven bean mdbName: jmsError\nException is : stack
Description
Cause
Action
Error: Error rolling back a JMS transaction for the message-driven bean mdbName: jmsError\nException is : stack
Description
Cause
Action
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
Cause
Action
Error: An error occurred while attempting to process a message inside a message-driven bean: error\nException is : stack
Description
Cause
Action
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
Cause
Action
Warning: Failed to undeploy security role for resource: resource, while undeploying EJB.
Description
Cause
Action
Warning: Failed to undeploy security policy for resource: resource, while undeploying EJB.
Description
Cause
Action
Info: The message-driven beans are being suspended. This may take a minute or two.
Description
Cause
Action
Info: The message-driven beans have all been suspended.
Description
Cause
Action
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
Cause
Action
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. The generated source files will be placed in outputDir.
Description
Info: Could not find a license for in-memory replication of the EJB. This feature is disabled;
Description
Error: Failed to create copy of bean: ejbName with error: trace.
Description
Cause
Action
Error: Failed to update secondary copy with : trace.
Description
Cause
Action
Error: Failure during stateful session bean replication: trace.
Description
Cause
Action
Error: Failure while updating secondary server during replication of: jndiName. The error was: trace.
Description
Cause
Action
Error: Failed to update the secondary copy of a stateful session bean from home:home.
Description
Cause
Action
Error: Skipping invalidation for component componentName (application= appName). Module had wrong type, className. 'weblogic.ejb20.deployer.EJBModule' was expected.
Description
Cause
Action
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
Cause
Action
Info: Exception occurred during the invocation of EJB "ejbName" with primary key "primKey":
Description
Cause
Action
Warning: The database type descriptorDatabaseType mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver driverDatabaseType.
Description
Cause
Action
Warning: WARNING(S) from EJB QL Compiler. \nwarning\n
Description
Cause
Action
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
Cause
Action
Error: A mismatch exists between the bean code and generated code.ejbName . Please rerun appc on the bean code. The error was errorMsg.
Description
Cause
Action
Error: Error encountered while attempting to create Default DBMS Table: 'tableName'. Error Text: 'text'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: EJB : ejbName .Unable to initialize method info for remote or home interface. The error is logmessage.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Duplicate EJB name ejbName in ejb-jar.xml.
Description
Cause
Action
Error: Errors encountered 'ejbName'.
Description
Cause
Action
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
Cause
Action
Error: For method 'finderName' in EJB 'ejbName': caching-name can not be specified if the query return type is not 'OBJECT'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error: The deployment descriptor 'fileName' was not found in 'jarName'. Please add this file to the JAR and try again.
Description
Cause
Action
Error: Problem: Could not find CMP Descriptor for EJB 'ejbName' in the CMPBeanDescriptor \n\nAction: Contact technical support for help.
Description
Cause
Action
Error: Problem: Could not find EnterpriseBeanMBean for EJB 'ejbName' in the EJBDescriptorMBean \n\nAction: Contact technical support for help.
Description
Cause
Action
Error: Problem: the EntityMBean for EJB 'ejbName' is not a version 'expectedVersion' Bean \n\nAction: Contact technical support for help.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Duplicate weblogic-rdbms-bean 'beanName' found in RDBMS CMP descriptor 'fileName'.
Description
Cause
Action
Error: Duplicate weblogic-rdbms-relation 'relationName' found in RDBMS CMP descriptor 'fileName'.
Description
Cause
Action
Error: Param must be an integer.
Description
Cause
Action
Error: Param must be an positive integer.
Description
Cause
Action
Error: Invalid field-group name. No field-group with the name 'groupName' was declared for this EJB in the RDBMS deployment descriptor.
Description
Cause
Action
Error: Bean with primary key 'pk' already exists.
Description
Cause
Action
Error: Bean with primary key: 'pk' not found.
Description
Cause
Action
Error: Creation of Many-To-Many relationship for primary key: 'pk1' and 'pk2' effected 'effected' rows in 'joinTableName', instead of just 1.
Description
Cause
Action
Error: Instance of EJB 'relatedEJBName' with primary key 'pk' does not exist.
Description
Cause
Action
Error: Optimistic concurrency violation. Instance of bean 'ejbName' with primary key 'pk' was changed by another transaction.
Description
Cause
Action
Error: The setXXX method for a primary key field may only be called during ejbCreate.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.
Description
Cause
Action
Error: In EJB 'ejbName', the primary key field 'pk' was not set during ejbCreate. All primary key fields must be initialized during ejbCreate.
Description
Cause
Action
Error: According to the EJB 2.0 specification, a value of ''null'' may not be assigned to a collection valued cmr-field.
Description
Cause
Action
Error: Field 'pkFieldName' not found in class 'pkClass'.
Description
Cause
Action
Error: An attempt was made to access a collection valued cmr-field outside the scope of a transaction.
Description
Cause
Action
Error: Illegal value for concurrency-strategy. Value was 'val', but must be one of 'ReadOnly', 'Exclusive','Database', or 'Optimistic'.
Description
Cause
Action
Error: Only instances of beans with a remote client view can invoke getEJBObject().
Description
Cause
Action
Error: Only instances of beans with a local client view can invoke getEJBLocalObject().
Description
Cause
Action
Error: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().
Description
Cause
Action
Error: Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction.
Description
Cause
Action
Error: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().
Description
Cause
Action
Error: Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction.
Description
Cause
Action
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
Cause
Action
Error: Security Violation: User: 'userName' has insufficient permission to access EJB: EJBResource.
Description
Cause
Action
Error: The handle was null.
Description
Cause
Action
Error: EJBObject from handle was null.
Description
Cause
Action
Error: handle.getEJBObject().getEJBHome() was null.
Description
Cause
Action
Error: The EJBObject represented by this handle is not from this EJBHome.
Description
Cause
Action
Error: Illegal attempt to invoke EJBMetaData.getPrimaryKeyClass() on a session bean.
Description
Cause
Action
Error: Error occurred while starting transaction: reason.
Description
Cause
Action
Error: Message-driven beans are not allowed to call methodName.
Description
Cause
Action
Error: Method 'methodName' has been declared in an assembly-descriptor exclude-list and cannot be executed.
Description
Cause
Action
Error: Security violation: insufficient permission to access method 'methodName'.
Description
Cause
Action
Error: No mapping from EJB Security Role to WLS Principal Name reason.
Description
Cause
Action
Error: Illegal attempt to call EJBObject.getPrimaryKey() on a session bean.
Description
Cause
Action
Error: Cannot remove stateless session beans using EJBHome.remove(Object primaryKey).
Description
Cause
Action
Error: env-entry for type java.lang.Character had length = 0.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: The resource-env-ref 'resourceEnvRefName' 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
Cause
Action
Error: Could not create a new JMS ConnectionFactory for the application: stackTrace.
Description
Cause
Action
Error: Could not resolve ejbLink: 'ejbLing'. The specified EJB could not be found in this application.
Description
Cause
Action
Error: Illegal attempt to call EJBLocalObject.getPrimaryKey() on a session bean.
Description
Cause
Action
Error: Illegal Reentrant call to 'ejbName' with primary key: 'pk'.
Description
Cause
Action
Error: The findByPrimaryKey method from home: 'ejbName' was passed: 'pk' but it returned null.
Description
Cause
Action
Error: The 'finderName' method from home: 'ejbName' returned null.
Description
Cause
Action
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
Cause
Action
Error: Unrecognized method name format for 'signature': Expected NAME or NAME() or NAME(arg1,arg2,...).
Description
Cause
Action
Error: Bean with primary key: 'pk' not created.
Description
Cause
Action
Error: Bean not found in 'finderMethodName'.
Description
Cause
Action
Error: Error encountered while attempting to drop Default DBMS Table: 'tableName'. Error Text: 'text'.
Description
Cause
Action
Error: Error encountered while attempting to alter Default DBMS Table: 'tableName'. Error Text: 'text'.
Description
Cause
Action
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
Cause
Action
Error: The alter table option is not supported in dbName. Please use the DropAndCreate option.
Description
Cause
Action
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
Cause
Action
Error: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().
Description
Cause
Action
Error: Security violation: User 'user' has insufficient permission to access method 'methodName'.
Description
Cause
Action
Error: 'exception' Linked exception = 'linked'
Description
Cause
Action
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
Cause
Action
Warning: An Exception occurred while uninitializing the EJB module moduleName:
Description
Cause
Action
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
Cause
Action
Warning: The EJB Module 'moduleName' has a class 'className' that contains a member. To update this class or any of its superclasses, redeploy the entire EJB Module. You cannot update these classes using the dynamic EJB impl class update feature.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Info: License validation not passed for ejbVersion.
Description
Info: ddl-file "ddlFileName" created.
Description
Info: ddl-file "ddlFileName" could not be deleted.
Description
Action
Info: Unable to write to ddl-file "ddlFileName"
Description
Info: Unable to alter the table as the primary key has changed.
Description
Action
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
Cause
Action
Info: Message-Driven EJB: ejbName's transaction was rolled back. The transaction details are: errorMessage.
Description
Cause
Error: Error starting MDB t
Description
Cause
Action
Info: The durable subscription store with jms-client-id equal to 'jmsClientID' is deleted when MDB 'ejbName' is removed from the server.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Warning: The Message-Driven EJB: ejbName is unable to bind to the JCA resource adapter: destName. The Error was:\nerrorMsg
Description
Cause
Action
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
Cause
Action
Info: EJB Deployed Message Driven Bean: beanFile
Description
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
Cause
Action
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
Cause
Action
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
Cause
Action
Info: EJB Exception occurred during invocation from home or business: ejbHome threw exception: throwable
Description
Error: Failed to update the secondary copy of a stateful session bean business:home.
Description
Cause
Action
Error: EJB : ejbName .Unable to initialize method info for remote ,home , message listener or webservice endpoint interface. The error is logmessage.
Description
Cause
Action
Error: Installation file fileName does not exist. Could not initialize EJB container-managed persistence.
Description
Cause
Action
Error: Installation file fileName is not readable. Could not initialize EJB container-managed persistence.
Description
Cause
Action
Error: Installation file fileName could not be opened. Could not initialize EJB container-managed persistence.
Description
Cause
Action
Error: Error occurred while loading persistence resource resourceName. Make sure that the persistence type is in your classpath.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Unable to create EJB Persistence Manager.
Description
Cause
Action
Error: Unable to bind EJB Home Interface to the JNDI name: jndiName.
Description
Cause
Action
Error: Unable to create a JNDI InitialContext to lookup the JMS destination.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: The Message-Driven EJB failed while creating a JMS Connection. The error was:\nmsg.
Description
Cause
Action
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
Cause
Action
Error: The persistence layer of the Entity EJB failed to deploy.
Description
Cause
Action
Error: Error while reading 'fileName'. The error was:\n errorMsg.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map. The error was:\nerrorMsg.
Description
Cause
Action
Error: Unable to create temporary directory: path. Please ensure that the server has write permission for this directory.
Description
Cause
Action
Error: An error occurred while reading the deployment descriptor. The error was:\n errorMsg.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
Description
Cause
Action
Error: The EJB container was unable to load the jts driver: weblogic.jdbc.jts.Driver. Please ensure that your classpath is set appropriately.
Description
Cause
Action
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
Cause
Action
Error: Could not get a connection from the DataSource with the JNDI name: dsName.
Description
Cause
Action
Error: Could not get a Connection from: name.
Description
Cause
Action
Error: The Entity EJB requires the table: tableName to be accessible. Please ensure that this table exists and is accessible.
Description
Cause
Action
Error: The container was unable to determine the java.sql.Types of database columns.
Description
Cause
Action
Error: Automatic Key Generation Error: could not get Generated PK Value. No RESULT from Query: genWLKeyGeneratorQuery.
Description
Cause
Action
Error: Automatic Key Generation: Error encountered while attempting setup and verify NAMED SEQUENCE TABLE tableName.
Description
Cause
Action
Error: Automatic Key Generation Error: Named Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.
Description
Cause
Action
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
Cause
Action
Error: Automatic Key Generation Error: attempted to UPDATE or QUERY NAMED SEQUENCE TABLE tableName, but encountered SQLException sqlException.
Description
Cause
Action
Error: Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to NAMED SEQUENCE TABLE tableName, but encountered Exception exception.
Description
Cause
Action
Error: Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Description
Cause
Action
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
Cause
Action
Error: ReadOnlyHome.invalidate from EJB:ejbName failed while attempting to send a multicast cache invalidation message.
Description
Cause
Action
Error: The pool poolName could not be found. Please make sure it is declared in your config.xml.
Description
Cause
Action
Error: Unable to create EJBRuntimeMBean.
Description
Cause
Action
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
Cause
Action
Error: Finder-expressions are no longer supported.
Description
Cause
Action
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
Cause
Action
Error: Unable to find bean 'ejbName' in an RDBMS CMP deployment descriptor.
Description
Cause
Action
Error: Finder Collection in 'sourceName' is NULL.
Description
Cause
Action
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
Cause
Action
Error: Error 'sourceName' received null when trying to get CMPBeanDescriptor for 'ejbName'.
Description
Cause
Action
Error: Duplicate 'type' 'Name' found. The 'type' is defined twice in two of the following descriptor files:
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Warning: In production mode the options ''DropAndCreate'',''DropAndCreateAlways'' and ''AlterOrCreate'' are ignored.The container would verify the table in this case.
Description
Cause
Action
Warning: The container was unable to create the ddl file.
Description
Cause
Action
Error: The container was unable to determine the java.sql.Types of database columns.
Description
Cause
Action
Info: Stack trace associated with message id follows: \n
Description
Cause
Action
Info: The following exception has occurred: \n
Description
Cause
Action
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
Cause
Action
Error: The ORACLE SEQUENCE named 'sequence' with INCREMENT 'increment' \n was not found in the database
Description
Cause
Action
Error: The ORACLE SEQUENCE named 'sequence' does not have INCREMENT value 'increment' \n in the database
Description
Cause
Action
Error: During EJB deployment, error(s) were encountered while setting up The ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
Warning: In production mode the options ''DropAndCreate'',''DropAndCreateAlways'' and ''AlterOrCreate'' are ignored. The container would verify the Oracle sequence in this case.
Description
Cause
Action
Error: During EJB deployment, error(s) were encountered while attempting to CREATE the ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
Error: During EJB deployment, error(s) were encountered while attempting to ALTER the ORACLE SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
Warning: In the
Description
Cause
Action
Warning: In the
Description
Cause
Action
Error: Unable to bind EJB Local Home Interface to the JNDI name: localJndiName.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Info: An exception occurred while starting the freepool idle timeout timer for ejb: 'ejbName', 'exceptionMsg'.
Description
Info: An exception occurred while stopping the freepool idle timeout timer for ejb: 'ejbName', 'exceptionMsg'.
Description
Info: An exception occurred while starting the Cache idle timeout timer for cache: 'cacheName', 'exceptionMsg'.
Description
Info: An exception occurred while stopping the Cache idle timeout timer for cache: 'cacheName', 'exceptionMsg'.
Description
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
Cause
Action
Error: The EJB specification prohibits stateful session beans from using the TimerService.
Description
Cause
Action
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
Cause
Action
Error: This Timer has either expired or been canceled and therefore cannot be invoked.
Description
Cause
Action
Error: The Timer associated with this TimerHandle has either expired or been canceled.
Description
Cause
Action
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
Cause
Action
Error: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB 'ejbName'.
Description
Cause
Action
Error: The following error occurred while attempting to remove an EJB Timer from the persistent store for EJB 'ejbName'.
Description
Cause
Action
Error: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB 'ejbName'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
Error: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
Error: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named 'sequence' with INCREMENT value 'increment' \n 'message'
Description
Cause
Action
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
Cause
Action
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, only have a single automatically generated database column per EJB.
Description
Cause
Action
Error: Automatic Key Generation: Error encountered while attempting setup and verify SEQUENCE TABLE tableName.
Description
Cause
Action
Error: Automatic Key Generation Error: Sequence Table tableName has no rows. Table must have a single row with a SEQUENCE column.
Description
Cause
Action
Error: Automatic Key Generation Error: Error while attempting to BEGIN a new transaction prior to FETCH of next key from Sequence Table: sqlException.
Description
Cause
Action
Error: Automatic Key Generation Error: attempted to UPDATE or QUERY SEQUENCE TABLE tableName, but encountered SQLException sqlException.
Description
Cause
Action
Error: Automatic Key Generation Error: attempted to do Local COMMIT of UPDATE to SEQUENCE TABLE tableName, but encountered Exception exception.
Description
Cause
Action
Error: Automatic Key Generation Error: Could not resume callers TX after UPDATE of Sequence Table tableName. Exception message exception.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Failed to register JACC policy context handlers for the ejb container
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error while reading 'META-INF/ejb-jar.xml' or 'fileName'. The error was:\n errorMsg.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.
Description
Cause
Action
Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be instantiated
Description
Cause
Action
Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' could not be found in the server classpath.
Description
Cause
Action
Error: Error in MDB EJB ejbName. The plugin-class 'pluginClass' does not implement weblogic.ejb.spi.SecurityPlugin.
Description
Cause
Action
Error: An unexpected error was encountered while attempting to remove any EJB Timers from the persistent store for the EJB 'ejbName'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error creating an instance of the EJB 'displayName': error
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error deploying EJB 'displayName'. While binding a business interface to JNDI the following error occurred: e
Description
Cause
Action
Error: Error deploying EJB 'displayName'. While binding a business interface to the JNDI name 'jndiName', the following error occurred: e
Description
Cause
Action
Error: Unable to bind Business Interface to the JNDI name: jndiName, throw exception e.
Description
Cause
Action
Error: Unable to bind Local Business Interface to the JNDI name: localJndiName, throw exception e.
Description
Cause
Action
Error: Method 'methodName' not found in interface 'sourceName'.
Description
Cause
Action
Error: While processing parameters for Automatic Key Generation. For generator-type: generatorType, the generator-name tag must specify the requiredSpecifier name.
Description
Cause
Action
Error: Error occurred while processing parameters for Automatic Key Generation. Unknown generator-type: generatorType. Allowed values are: ORACLE, SQL_SERVER, NAMED_SEQUENCE_TABLE.
Description
Cause
Action
Error: Error occurred while processing parameters for Automatic Key Generation. Encountered unknown
Description
Cause
Action
Error: When Automatic Key Generation is enabled, the Primary Key cannot be part of the Foreign Key to another bean.
Description
Cause
Action
Error: In 'source', unable to load Class 'className'.
Description
Cause
Action
Error: Field 'field' not found in class 'class'.
Description
Cause
Action
Error: Could not generate Finder method code for type 'finder' due to EJBCException: 'exceptionMessage'.
Description
Cause
Action
Error: NULL finder in 'target'.
Description
Cause
Action
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
Cause
Action
Error: Could not find any HomeClass Name for Finder Expression in Finder: 'finder'.
Description
Cause
Action
Error: Could not find any Remote Finder Node for Finder: 'finder'.
Description
Cause
Action
Error: Could not find any RemoteHomeName checked for RemoteFinderNode or Remote ParamNode and found neither for Finder: 'finder'.
Description
Cause
Action
Error: Method 'method' in interface 'interface' has wrong Parameter count, expected: expectedParamCount.
Description
Cause
Action
Error: Remote Finder in Finder 'finder': Remote Finder Name is null.
Description
Cause
Action
Error: Expected to get 'target' for finder 'finder', but we got null instead.
Description
Cause
Action
Error: Expected to get entry in beanMap for 'ejbName', but got null instead.
Description
Cause
Action
Error: Error while generating target.
Description
Cause
Action
Error: Error while compiling Query with Remote Finder unknown Remote Finder Command: 'command'.
Description
Cause
Action
Error: Could not produce production rule for target.
Description
Cause
Action
Error: In Finder 'finderName', could not get Class for cmpField 'field'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE 'publicId' not permitted. Only DOCTYPE 'correctDocType' permitted here.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Info: Compiling generated EJB classes produced the following Java compiler output:\noutput
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Compiling generated EJB classes produced the following Java compiler error message:\noutput
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Expression 'exprType' has incorrect number of terms: termCount.
Description
Cause
Action
Error: Expression 'exprType' requires a requirement.
Description
Cause
Action
Error: Parameters in EJB QL must be numbered 1 or greater. Finder 'finder' has a parameter numbered: 'badParamNum'. This must be corrected.
Description
Cause
Action
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
Cause
Action
Error: in 'inClause'; clause: could not get Class corresponding to cmp-field: 'cmpField' in path: 'id' for Bean: 'ejbName'.
Description
Cause
Action
Error: Error encountered while attempting to get target for for: 'exception'.
Description
Cause
Action
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
Cause
Action
Error: SELECT clause processing could NOT find JoinNode for 'id' in JoinTree. Please double check your EJB QL query for correctness.
Description
Cause
Action
Error: An EJB QL Query requires a SELECT clause at the beginning of the query.
Description
Cause
Action
Error: An EJB QL Query requires a FROM clause following the SELECT clause in the Query.
Description
Cause
Action
Error: First term of range_variable_declaration 'id' cannot be a Path Expression. It can only be an abstract_schema_name.
Description
Cause
Action
Error: Could not get abstractSchemaName from ejb-jar.xml for comparison to input range_variable_declaration 'id'.
Description
Cause
Action
Error: Could not get an abstract schema name from ejb-jar.xml for entity bean 'ejbName'. An abstract schema name is required.
Description
Cause
Action
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
Cause
Action
Error: function argument must be a single valued path expression.
Description
Cause
Action
Error: Exception occurred while trying to get last JoinNode in path for relationshipType. Path ID 'pathId' 'exceptionText'
Description
Cause
Action
Error: Expected a single Foreign Key Column for relationshipType in path expression: 'pathId'. Instead, found: foundSize
Description
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Could not find cmr-field in Bean: 'ejbNameFrom' that points to EJBean: 'ejbNameTo'.
Description
Cause
Action
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
Cause
Action
Error: Bean: 'ejbName' cmr-field: 'cmrField' relationshipType, expected cmr-field to be a foreign key field but apparently it is not.
Description
Cause
Action
Error: Bean: 'ejbName' cmr-field: 'cmrField' could not get Foreign Key Column Names for 'command'.
Description
Cause
Action
Error: Error argument to 'command' must be a collection valued path expression.
Description
Cause
Action
Error: Error: could not get Join Table.
Description
Cause
Action
Error: Error: could not get Foreign Key Table.
Description
Cause
Action
Error: Left Hand argument to [NOT] MEMBER [OF] must be either a single_valued_path_expression or in input parameter.
Description
Cause
Action
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
Cause
Action
Error: Right-hand argument to [NOT] MEMBER [OF] must be a collection_valued_path_expression.
Description
Cause
Action
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
Cause
Action
Error: Could not get pkClass for pkField: 'field'.
Description
Cause
Action
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
Cause
Action
Error: Could not get Table Alias List.
Description
Cause
Action
Error: Expected a Boolean literal of TRUE or FALSE, but received neither.
Description
Cause
Action
Error: Could not obtain Table and Field for 'id'.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Error Path Expression ends in x, not y.
Description
Cause
Action
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
Cause
Action
Error: The Identifier 'argument' is neither a cmp-field nor a cmr-field. Re-examine your query.
Description
Cause
Action
Error: TOKEN 'SPECIAL' 'specialName' has no counterpart in EJB QL. Finder Expressions are not supported. Cannot translate.
Description
Cause
Action
Error: Attempted to define the Identifier 'specialName' in an AS clause more than once. You may only define 'specialName' once.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Sub-queries that SELECT beans cannot be compared to Variables (e.g. ?1). This is not supported.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: 'op' argument is not of type IDENTIFIER or INTEGER. Found an argument of type 'bad_type'. Re-examine your query.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Cannot do Outer Join between Bean: 'bean1' and Bean: 'bean2' for Database 'database'. No database support for SQL Outer Join.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: Duplicate AS definition of 'Id' in FROM clause.
Description
Cause
Action
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
Cause
Action
Error: Error, could not find Range Variable, as declared in FROM clause, for EJBean: 'ejbName' with AbstractSchemaName: 'abstractSchemaName'.
Description
Cause
Action
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
Cause
Action
Error: Correlation variable 'id' is defined more than once.
Description
Cause
Action
Error: The pathExpression/Identifier 'id' contains a root: 'asID' that is not defined in an AS declaration in the FROM clause.
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Error: ''NOT'' Expressions have been factored out and removed to preserve any generated SQL joins.
Description
Cause
Action
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
Cause
Action
Error: Invalid relationship-caching name. No relationship-caching with the name 'cachingName' was declared for this EJB in the RDBMS deployment descriptor.
Description
Cause
Action
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
Cause
Action
Error: Problem, encountered illegal value for transaction-isolation 'readValue' \n\nAction. Specify a legal value: TransactionSerializable | TransactionReadCommitted | TransactionReadCommittedForUpdate | TransactionReadCommittedForUpdateNoWait | TransactionReadUncommitted | TransactionRepeatableRead
Description
Cause
Action
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
Cause
Action
Error: Duplicate relation name 'name' found while processing ejb-jar deployment descriptor. The ejb-relation-name values must be unique.
Description
Cause
Action
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
Cause
Action
Warning: Warning: In EJB ejbName,
Description
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
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
Cause
Action
Info: The EJB 'ejbName' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:
Description
Info: ******** businessIntfName is bound with JNDI name:jndiName ********
Description
Info: Cannot invoke stateful callback on beanType
Description
Info: Unable to bind the interface interfaceName to name. Another EJB has already bound an interface to that name."
Description
Info: Unable to bind the interface interfaceName to name. This EJB has declared another interface already bound to that name
Description
Info: Error during 'name'. Couldn't get connection: \n exception \ntrace
Description
Info: Error during finder 'name'. Exception while preparing query: 'query'\n exception \ntrace
Description
Info: Couldn't get connection: \nexception\ntrace
Description
Info: Error constructing query: \nexception\ntrace
Description
Info: Error calling getDatabaseProductName: \nexception\ntrace
Description
Info: Error calling getDatabaseProductVersion: \nexception\ntrace
Description
Info: Error during finder 'name'. Exception while setting parameters for query 'query'\nexception\ntrace
Description
Info: Error during finder 'name'. Exception while executing query 'exception'\ntrace
Description
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
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
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
Info: A stored procedure or function is used by 'name', but no SqlShape is specified.
Description
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
Info: Query-caching is not supported for read-write beans
Description
Info: Error obtaining nativeQuery: msg, excep
Description
Info: Attempt to do executeQuery on query 'query', using a non-WebLogic EntityManager
Description
Info: Internal Error: Extended Persistence Context has been closed!!!!
Description
Info: attempt at illegal state transaction from oldState to state
Description
Info: Illegal call to EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces
Description
Info: The EJB name is not a EJB3.0 bean!
Description
Info: The EJB bean doesn't declare a local home interface!
Description
Info: The EJB bean does not implement the business interface interface
Description
Info: the bean has not been invoked through a business interface .
Description
Info: It is illegal to invoke UserTransaction methods in ejbCreate or PostConstruct method of message driven bean.
Description
Info: It is illegal to invoke UserTransaction methods in ejbRemove or PreDestroy method of message driven bean.
Description
Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of message driven bean.
Description
Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of stateful session bean.
Description
Info: It is illegal to invoke UserTransaction methods in ejbCreate or PostConstruct method of stateless session bean.
Description
Info: It is illegal to invoke UserTransaction methods in ejbRemove or PreDestroy method of stateless session bean.
Description
Info: It is illegal to invoke UserTransaction methods in setSessionContext or dependency injection of stateless session bean.
Description
Info: Single expiration timers cannot be cancelled from within ejbTimeout
Description
Info: It''s illegal to invoke Timer methods in ejbRemove or PreDestroy method from session bean or MDB
Description
Info: It''s illegal to invoke Timer methods in ejbActivate or PostActivate method
Description
Info: It''s illegal to invoke Timer methods in ejbPassivate or PrePassivate method
Description
Info: it''s illegal to invoke Timer methods during dependency injection
Description
Info: Invocation timed out. Timer is busy.
Description
Info: Error cancelling timer.
Description
Info: EjbJarBean not set yet
Description
Info: Method method is marked TX_NEVER, but was called within a transaction.
Description
Info: Unexpected exception in afterDelivery(): exception
Description
Info: Attempt to execute getDatabaseProductName using a non-WebLogic EntityManager.
Description
Info: Error calling getDatabaseProductName: stack
Description
Info: Attempt to execute nativeQuery on query 'query', using a non-WebLogic EntityManager.
Description
Info: Error obtaining nativeQuery: stack
Description
Info: Error preparing query: stack
Description
Info: encounter a remote exception, the nested exception is:
Description
Info: Error adding handler chain: errorMsgs
Description
Info: @EJB annotation doesn''t have beanInterface set
Description
Info: A class level type annotation on class class does not have the name attribute set.
Description
Info: A class level Resource annotation on class class does not have the type attribute set
Description
Info: Illegal attempt to make a reentrant call to a stateful session bean: name
Description
Info: Illegal attempt to make a reentrant call to a stateful session bean from home: name
Description
Info: Unable to link class class in Jar jar : exception
Description
Info: Unable to load class class in Jar jar : exception
Description
Info: Unable to create virual Jar jar : exception
Description
Info: The super class superClass of session bean class class is also a session bean class.
Description
Info: session type are not set in deployment descriptor or annotation for session bean class
Description
Info: The session bean name does not have a client view specified. Since the bean class class implements multiple interfaces, 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
Info: No ejbCreate method was found for init method: method in bean class
Description
Info: No matching create method for @Init method: method in bean class
Description
Info: Couldn't load interceptor class class: exceptionMsg
Description
Info: In bean class , there are multiple method permission annotations for method: method ,which is illegal.
Description
Info: There are multiple method permission annotations for class: class ,which is illegal.
Description
Info: Unable to load interface class class: exception
Description
Info: Bean class class doesn't implement interface method: method.
Description
Info: ServiceEndpoint class:class was specified but can not be found.
Description
Info: The super class superClass of message-driven bean class class is also a message-driven bean class.
Description
Info: MDB class implements multiple interfaces and no messageListenerInterface was specified in the @MessageDriven annotation
Description
Info: In bean class class, @EJB annotation is at class level, so beanInterface must be explicitly specified
Description
Info: In interceptor class class , @EJB annotation is at class level, so beanInterface must be explicitly specified
Description
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
Description
Error: Cannot specify @JNDIName on both the remote interface and the implementation class. Class: clsName; interface: ifaceName.
Description
Cause
Action
Error: Cannot specify @JNDIName on the implementation for a class with multiple remote interfaces. Class: clsName; interfaces: ifaces.
Description
Cause
Action
Error: annoType is not valid in this context. Bean class: clsName.
Description
Cause
Action
Error: annoType is not valid in this context. Bean method: clsName.methName.
Description
Cause
Action
Error: Couldn't specify @JNDIName on local business interface: interface of Bean:beanName.
Description
Cause
Action
Error: Unable to load a class specified in your ejb-jar.xml: msg.
Description
Cause
Action
Error: Reference name 'name' of @annotationName annotation on class className is not unique.
Description
Cause
Action
|
