EclipseLink Exception Error Reference (ELUG)

Related topics

This section lists EclipseLink exceptions and provides numerical ranges of their error codes. Each exception code corresponds to an exception class and includes the following information:

• The exception number in the format of EXCEPTION [ECLIPSELINK-XXXX]
• A description of the problem, taken from the raised exception

Descriptor Exceptions (1 – 202)

DescriptorException is a development exception that is raised when insufficient information is provided to the descriptor. The message that is returned includes the name of the descriptor or mapping that caused the exception. If a mapping within the descriptor caused the error, then the name and parameters of the mapping are part of the returned message, as this exampledemonstrates.

Internal exception, mapping and descriptor appear only if EclipseLink has enough information about the source of the problem to provide this information.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
INTERNAL EXCEPTION: Message
MAPPING: Database mapping
DESCRIPTOR: Descriptor

Descriptor Exception

EXCEPTION [ECLIPSELINK – 75]: org.eclipse.persistence.exceptions.DescriptorException
EXCEPTION DESCRIPTION: The reference class is not specified.

Concurrency Exceptions (2001 – 2009)

ConcurrencyException is a development exception that is raised when a Java concurrency violation occurs. Only when a running thread is interrupted, causing the JVM to throw an InterruptedException, is an internal exception information displayed with the error message, as this exampleshows.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
INTERNAL EXCEPTION: Message

Concurrency Exception

EXCEPTION [ECLIPSELINK – 2004]: org.eclipse.persistence.exceptions.ConcurrencyException
EXCEPTION DESCRIPTION: Signal attempted before wait on concurrency manager. 
This usually means that an attempt was made to commit or roll back a transaction before being started, or rolled back twice.

Conversion Exceptions (3001– 3008)

ConversionException is a development exception that is raised when a conversion error occurs by an incompatible type conversion. The message that is returned indicates which type cast caused the exception.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
INTERNAL EXCEPTION: Message

Conversion Exception

EXCEPTION [ECLIPSELINK – 3006]: org.eclipse.persistence.exceptions.ConversionException
EXCEPTION DESCRIPTION: object must be of even length to be converted to a ByteArray

Database Exceptions (4003 – 4018)

DatabaseException is a run-time exception that is raised when data read from the database, or the data that is to be written to the database, is incorrect. The exception may also act as a wrapper for SQLException. If this is the case, the message contains a reference to the error code and error message, as shown in this example

This exception can occur on any database operation. If an execution of a SQL script is involved in a database operation causing DatabaseException, the exception's message, accessible through the getMessage method, contains the SQL that caused this exception.

This exception includes internal exception and error code information when the exception is wrapping a SQLException.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
INTERNAL EXCEPTION: Message
ERROR CODE: Error code

Database Exception

EXCEPTION [ECLIPSELINK – 4002]: org.eclipse.persistence.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: [INTERSOLV][ODBC dBase driver] Incompatible datatypes in expression: >

INTERNAL EXCEPTION: java.sql.SQLException: [INTERSOLV][ODBC dBase driver] Incompatible datatypes in expression: >
ERROR CODE: 3924

Optimistic Lock Exceptions (5001 – 5009)

OptimisticLockException is a run-time exception that is raised when the row on the database that matches the desired object is missing or when the value on the database does not match the registered number. It is used in conjunction with the optimistic locking feature. This applies only on an update or delete operation, as shown in this example.

For more information about optimistic locking, see the section on optimistic locking in a stateless environment in Introduction to EclipseLink Application Development (ELUG). These exceptions should be handled in a try-catch block.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception Name
EXCEPTION DESCRIPTION: Message

Optimistic Lock Exception

EXCEPTION [ECLIPSELINK – 5003]: org.eclipse.persistence.exceptions.OptimisticLockException
EXCEPTION DESCRIPTION: The object, object.toString() cannot be deleted because it has changed or been deleted since it was last read.

Query Exceptions (6001 – 6129)

QueryException is a development exception that is raised when insufficient information has been provided to the query. If possible, the message indicates the query that caused the exception. A query is optional and is displayed if EclipseLink is able to determine the query that caused this exception, as shown in this example

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message
QUERY:

Query Exception

EXCEPTION [ECLIPSELINK – 6026]: org.eclipse.persistence.exceptions.QueryException
EXCEPTION DESCRIPTION: The query is not defined. When executing a 
query on the session, the parameter that takes the query is null.

Validation Exceptions (7001 – 7200)

ValidationException is a development exception that is raised when an incorrect state is detected or an API is used incorrectly.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Validation Exception

EXCEPTION [ECLIPSELINK – 7008]: org.eclipse.persistence.exceptions.ValidationException
EXCEPTION DESCRIPTION: The Java type javaClass is not a valid database type. The Java type of the field to be written to the database has no corresponding type on the database.

EJB QL Exceptions (8001 – 8010)

EJBQLException is a run-time exception that is raised when the EJB QL string does not parse properly, or the contents cannot be resolved within the context of the EclipseLink session. The associated message typically includes a reference to the EJB QL string that caused the problem.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

EJB QL Exception

EXCEPTION [ECLIPSELINK – 8002]: org.eclipse.persistence.exceptions.EJBQLException
EXCEPTION DESCRIPTION: EclipseLink has encountered a problem while parsing the EJB QL string.

Session Loader Exceptions (9000 - 9010)

SessionLoaderException is a run-time exception that is raised if the session manager encounters a problem loading session information from a sessions.xml (for non-EJB applications)

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Session Loader Exception

EXCEPTION [ECLIPSELINK – 9004]: org.eclipse.persistence.exceptions.SessionLoaderException
EXCEPTION DESCRIPTION: The <project-xml> file MyProject was not found on the classpath, nor on the filesystem.

EJB Exception Factory Exceptions (10001 - 10070)

An EJB exception factory generates run-time exceptions that are raised if a container provider specific to a given application server encounters a problem during any stage of the life cycle of an EJB bean.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

EJB Exception Factory Exception

EXCEPTION [ECLIPSELINK – 10008]: javax.ejb.CreateException
EXCEPTION DESCRIPTION: Cannot find bean.

Communication Exceptions (12000 - 12003)

CommunicationException is a run-time exception that wraps all RMI, CORBA, or input and output exceptions that occur.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Communication Exception

EXCEPTION [ECLIPSELINK – 12000]: org.eclipse.persistence.exceptions.CommunicationException
EXCEPTION DESCRIPTION: Error Sending connection service to myService.

EIS Exceptions (17007 – 17025), 90000, 91000

EISException is a run-time exception that is raised when invoking EIS interactions. For more information on EIS interactions, see Enterprise Information System (EIS) Interactions.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

JMS Processing Exception

EXCEPTION [ECLIPSELINK – 17010]: org.eclipse.persistence.eis.EISException
EXCEPTION DESCRIPTION: Output record contains an unsupported message type.

JMS Processing Exceptions (18001 - 18004)

JMSProcessingException is a run-time exception that is raised when processing JMS messages.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

JMS Processing Exception

EXCEPTION [ECLIPSELINK – 18001]: org.eclipse.persistence.exceptions.JMSProcessingException
EXCEPTION DESCRIPTION: Error while processing incomming JMS message.

Default Mapping Exceptions (20001 - 20008)

DefaultMappingException is a run-time exception that is raised when an error occurs during OC4J CMP default mapping.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Default Mapping Exception

EXCEPTION [ECLIPSELINK – 20002]: org.eclipse.persistence.exceptions.DefaultMappingException
EXCEPTION DESCRIPTION: The finder method with the parameters as defined in the ejb-jar.xml file, is not found in the home of bean.

Discovery Exceptions (22001 - 22004)

DiscoveryException is a run-time exception that is raised when DiscoveryManager is operating.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Discovery Exception

EXCEPTION [ECLIPSELINK – 22001]: org.eclipse.persistence.exception.DiscoveryException
EXCEPTION DESCRIPTION: Could not join multicast group.

Remote Command Manager Exceptions (22101 - 22111)

RemoteCommandManagerException is a run-time exception that is raised when the remote command module is used.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Remote Command Manager Exception

 EXCEPTION [ECLIPSELINK – 22104]: org.eclipse.persistence.exceptions.RemoteCommandManagerException
EXCEPTION DESCRIPTION: Could not look up host name.

Transaction Exceptions (23001 - 23015)

TransactionException is a run-time exception that is raised when an error is encountered during a transaction. When this occurs, the message contains a reference to the error code and error message.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception nameEXCEPTION DESCRIPTION: Message

Transaction Exception

EXCEPTION [ECLIPSELINK – 23001]: org.eclipse.persistence.exceptions.TransactionExceptionEXCEPTION DESCRIPTION: Error looking up external Transaction resource under JNDI name.

XML Conversion Exceptions (25501)

XMLConversionException is a run-time exception that is raised when a conversion between EclipseLink instances and XML fails. This exception is used in cache coordination that uses XML change sets.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

XML Conversion Exception

EXCEPTION [ECLIPSELINK – 25001]: org.eclipse.persistence.exceptions.XMLConversionException
EXCEPTION DESCRIPTION: Cannot create URL for file  [\\FILE_SERVER\command.xml].

XML Marshal Exceptions (25001 – 25020)

XMLMarshalException is raised when an error is encountered during the XML marshalling process.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

XML Marshal Exception

EXCEPTION [ECLIPSELINK – 25001]: org.eclipse.persistence.exceptions.XMLMarshalException
EXCEPTION DESCRIPTION: Error while trying to create session.

Migration Utility Exceptions (26001 - 26020)

MigrationUtilityException is a run-time exception that is raised when an error is encountered during the use of the EclipseLink migration utility.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Migration Utility Exception

EXCEPTION [ECLIPSELINK – 26002]: org.eclipse.persistence.exceptions.MigrationUtilityException
EXCEPTION DESCRIPTION: The program security manager prevents the migration utility from creating a JAR class loader for the JAR file.

XML Platform Exceptions (27001 – 27006, 27101 – 27103, 27201 – 27202)

XMLPlatformException is raised when an error related to XML platform is encountered.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

EJB JAR XML Exception

EXCEPTION [ECLIPSELINK – 27001]: org.eclipse.persistence.platform.xml.XMLPlatformException
EXCEPTION DESCRIPTION: The XML platform class ClassName was not found.

Entity Manager Setup Exceptions (28001 – 28007)

EntityManagerSetupException is raised when an error is encountered during the process of setting up an entity manager.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

Entity Manager Setup Exception

EXCEPTION [ECLIPSELINK – 28001]: org.eclipse.persistence.exceptions.EntityManagerSetupException
EXCEPTION DESCRIPTION: Error while trying to create session.

EJB JAR XML Exceptions (72000 – 72023)

EJBJARXMLException is a run-time exception that is raised at deployment time when the ejb-jar.xml file is read and the required concrete EJB classes code is generated.

Format

EXCEPTION [ECLIPSELINK – error code]: Exception name
EXCEPTION DESCRIPTION: Message

EJB JAR XML Exception

EXCEPTION [ECLIPSELINK – 72000]: org.eclipse.persistence.exceptions.EJBJarXMLException
EXCEPTION DESCRIPTION: Error reading ejb-jar.xml file.

---

Copyright Statement