Previous Contents Index Next |
Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Error Messages Reference

> ## Chapter 9
> Enterprise Java Beans

> This chapter lists error messages that originate from the enterprise java bean subsystem.

> ##

> EJB

> An enterprise java bean (EJB) is a server-side component that encapsulates the business logic of an application. The business logic is the code that fulfills the purpose of the application.

> ##### EJB5013

> Severity | SEVERE
> Description | An internal EJB exception occurred.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5014

> Severity | SEVERE
> Description | An internal exception occurred while resolving an object.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5016

> Severity | SEVERE
> Description | An exception occurred while creating BaseContainer. Possible reasons are: The ejbObject class/home interface, or class/remote interface class could not be loaded. An exception occurred while trying to bind the objects into the Naming manager.
> Action | More information on the exception can be obtained from the log file. Correct the problem and redeploy the application.

> ##### EJB5017

> Severity | SEVERE
> Description | An exception occurred while running preinvoke.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5020

> Severity | WARNING
> Description | An exception occurred while unregistering monitormbean. This exception occurs if the MBean is not registered for a particular EJB. Another reason may be incorrectly unregistering from the MBean server.
> Action | Make sure that the MBean is not registered for a particular EJB. Ensure that you unregister from the MBean server correctly.

> ##### EJB5021

> Severity | SEVERE
> Description | The session bean transaction is incomplete.
> Action | A transaction started within a method of the stateless session bean must be completed before leaving the method. Check the application code and correct the problem.

> ##### EJB5022

> Severity | SEVERE
> Description | Message driven bean transaction is incomplete.
> Action | A transaction started within a method of a Message Driven Bean must be completed before leaving the method. Check the application code and correct the problem.

> ##### EJB5023

> Severity | SEVERE
> Description | An exception occurred while registering monitormbean.
> Action | An MBean with a similar configuration is already registered or an error occurred while registering the bean with the MBean server.

> ##### EJB5024

> Severity | WARNING
> Description | An exception occurred while registering child monitormbean in the pool/cache to the monitoring bean.
> Action | Refer the stack trace for details. If you are unable to fix the error, Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5025

> Severity | WARNING
> Description | An internal exception occurred while releasing EJB context back to the pool.
> Action | Refer the stack trace for details on how to correct the problem. If you are unable to fix the error, Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5026

> Severity | SEVERE
> Description | An exception occurred while removing the EJB local object. When the ejbRemove() method of the bean was called, the method sent a RemoveException.
> Action | Check the application code.

> ##### EJB5027

> Severity | SEVERE
> Description | An exception occurred while removing the EJB. When the ejbRemove() method of the bean was called, the method sent an exception.
> Action | Check the stack trace information to correct the problem. If you still get the error, Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5028

> Severity | SEVERE
> Description | An exception occurred while getting the EJB local object. Possible reason could be, an EJB object instance could not be created.
> Action | Make sure that the bean class is defined as public and has a default constructor.

> ##### EJB5029

> Severity | SEVERE
> Description | An exception occurred while getting the EJB context. Possible reasons could be, an EJB object instance could not be created.
> Action | Make sure that the bean class is defined as public and has a default constructor.

> ##### EJB5030

> Severity | SEVERE
> Description | An exception occurred while comparing homes and primary keys of two EJBs.
> Action | Make sure that the EJBObject passed as parameter to the isIdentical method is not null.

> ##### EJB5031

> Severity | SEVERE
> Description | A remote exception occurred while refreshing a Read Only bean or the bean name was incorrectly specified.
> Action | Make sure the bean is not a remote object or a Read Only bean. Check the code to specify the correct bean name. If the bean does not provide a remote interface, use the getReadOnlyBeanLocalNotifier to refresh the local Read Only bean. Otherwise, set the is-read-only-bean to true in the sun-ejb-jar.xml file.

> ##### EJB5032

> Severity | SEVERE
> Description | An exception occurred while creating a new bean. Possible reason could be, a bean instance could not be created.
> Action | Make sure the bean class is defined as public and has a default constructor.

> ##### EJB5058

> Severity | SEVERE
> Description | The passivation directory could not be created. This occurs if you do not have Write access permission to the directory pointed by the session-store element in the server.xml of the server instance.
> Action | Make sure you have Write access permission to the directory pointed by the session-store element in the server.xml of the server instance

> ##### EJB5059

> Severity | SEVERE
> Description | An exception occurred while creating a new bean. Possible reason could be, a bean instance that could not be created.
> Action | Make sure the bean class is defined as public and has a default constructor.

> ##### EJB5060

> Severity | SEVERE
> Description | An exception occurred while creating a new bean. Possible reason could be, a bean instance that could not be created.
> Action | Make sure the bean class is defined as public and has a default constructor.

> ##### EJB5061

> Severity | SEVERE
> Description | Unable to call remove on the statefulsession bean. The bean may be removed due to time-out.
> Action | Set higher values for removal-timeout in server.xml. If you still get this error, Analyze the System, as described on (more...) with the server log and stack trace information.

> ##### EJB5062

> Severity | SEVERE
> Description | An exception occurred while removing the bean.
> Action | Set higher values for removal-timeout in server.xml If you still get this error, Analyze the System, as described on (more...) with the server log and stack trace information.

> ##### EJB5063

> Severity | SEVERE
> Description | Unable to call remove on the stateful session bean. The bean may be removed due to time-out.
> Action | Set higher values for removal-timeout in server.xml If you still get this error, Analyze the System, as described on (more...) with the server log and stack trace information.

> ##### EJB5064

> Severity | SEVERE
> Description | An exception occurred in the code implementing the afterCompletion method of the SessionSynchronization interface.
> Action | Look at the afterCompletion code in your session bean that implements the SessionSynchronization interface.

> ##### EJB5066

> Severity | SEVERE
> Description | An exception occurred in the ejbRemove() method of the Stateful session bean, other than EJBException or EJBRemoveException.
> Action | See the log file that contains the stack trace describing the cause of the exception. If you still get this error, Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5069

> Severity | SEVERE
> Description | An exception occurred getting the ejbcreate() method.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5070

> Severity | SEVERE
> Description | An exception occurred while creating stateless session bean.
> Action | See the log file that contains the stack trace describing the cause of the exception. If this error occurs again, Analyze the System, as described on (more...) .

> ##### EJB5071

> Severity | SEVERE
> Description | A remote or transactional roll back exception occurred when the container attempted to commit or rollback the transaction. Typically, a database failure (like database server crash) causes this failure.
> Action | See the stack trace for more information.

> ##### EJB5103

> Severity | SEVERE
> Description | An exception occurred in releaseContext.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5105

> Severity | WARNING
> Description | An exception occurred in createContainer.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> ##### EJB5106

> Severity | WARNING
> Description | An exception occurred in EntityContainer.
> Action | Analyze the System, as described on (more...) with the stack trace information.

> Previous Contents Index Next

> Copyright 2004 Sun Microsystems, Inc. All rights reserved.