Oracle GlassFish Server 3.0.1 Error Message Reference

EJB


EJB5013 Some EJB exception occurred : [{0}]

Cause:

Problem occurred while deserializing stateful bean state.

Solution:

Check the application classpath to ensure that all classes needed during deserialization are available.


EJB5017 Exception while running pre-invoke : ejbName = [{0}]

Cause:

An error occurred during the removal of an entity bean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean.

Solution:

Check the exception stack trace to see if the exception originated from the entity bean implementation class.


EJB5031 Some remote exception occurred while refreshing rob : [{0}] : [{0}]

Cause:

An error occurred while looking up a Read Only Bean Notifier. The most common cause for this failure is that the string supplied to the getReadOnlyBeanNotifier method either does not refer to a read-only bean.

Solution:

Check the application code that calls this method to make sure the string passed in refers to a valid read-only bean.


EJB5069 Exception getting ejbcreate method : [{0}]

Cause:

The bean's Home or LocalHome does not define a no-arg create method.

Solution:

Check the Home or LocalHome interface for the appropriate create method signature. Running the verifier will help identify the error as well.


EJB5071 Some remote or transactional roll back exception occurred

Cause:

Some problem occurred during the beforeCompletionphase of the transaction lifecycle. This error often happens when application code throws a system exception from its ejbStore method or if the transaction manager encounters a system exception.

Solution:

Check the stack trace to see if the exception originated from the application's ejbStore method. Also check the resource configuration to ensure that all resource managers involved in the transaction are configured properly and healthy.


EJB5090 Exception in creating EJB container [{0}]

Cause:

Problem during ejb container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, class-not-found errors, and configuration errors for resources needed by the ejb.

Solution:

If the ejb has a Remote view, check that its JNDIname does not clash with any other ejb's JNDI name or any other globalJNDI name. Check that all needed classes are available to the ejb. Also ensure that any resources needed by the ejb are available. If the ejb uses a datasource make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created.


EJB5111 Bean class for ejb [{0}] does not define a method corresponding to [{1}] interface method [{2}]

Cause:

This error indicates a mismatch in the required method signature rules between a method defined on a [Home, Remote, LocalHome, Local] interface and the corresponding bean implementation class. E.g., this would happen if a create method in a Home interface did not have a matching ejbCreate method in the bean class.

Solution:

Run the verifier tool to check that the methods defined on the bean class are correct with respect to the exposed interface.


EJB5117 Timer creation failed for container [{0}] primary key [{1}] and info [{2}]

Cause:

Error while creating the persistent representation of an ejb timer. This typically means there is some configuration error or runtime problem with the ejb timer service datasource.

Solution:

Double-check the JDBC datasource (and its associated connection pool) assigned to the timer-datasource element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect.


EJB5128 Error during Stateful Session Bean activation for key [{0}]

Cause:

A problem occurred while the container was activating a stateful session bean. One possible cause is that the bean code threw a system exception from its ejbActivate method.

Solution:

Check the stack trace to see whether the exception was thrown from the ejbActivate method and if so double-check the application code to determine what caused the exception.


EJB5129 Error in ContainerSynchronization::afterCompletion

Cause:

An error occurred during the afterCompletion phase of the transaction lifecycle.

Solution:

Check stack trace for details of error encountered by ejb container


EJB5169 Exception while running preinvoke

Cause:

An error occurred during the call to preInvoke of the EjbSecurityComponentInvocationHandler.

Solution:

Check the exception stack trace to see if the exception originated from EjbSecurityManager.


EJB5170 Exception while running postInvoke

Cause:

An error occurred during the call to postInvoke of the EjbSecurityComponentInvocationHandler.

Solution:

Check the exception stack trace to see if the exception originated from EjbSecurityManager.


EJB5173 No EJB modules found

Cause:

No EJB modules had been found on the classpath or specified via MODULE property.

Solution:

Check the classpath and the value(s) of the MODULE property.


EJB5174 Cannot determine server installation location

Cause:

Installation location is not specified, and cannot be determined relative to the implementation location.

Solution:

Check the classpath or specify server installation location using the org.glassfish.ejb.embedded.glassfish.installation.root property


EJB5175 Temporary file could not be created: {0}

Cause:

See output for details.

Solution:

See detailed exception at FINE log level.