Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Common IBM WebSphere Application Server Exceptions

When the IBM WebSphere application server is started, it attempts to deploy the JAR files that are specified for deployment within the application server.

Exceptions that occur when the server is started are usually configuration problems that involve classpath issues, environment variable configuration, and database login configuration. Review the IBM WebSphere application server documentation after starting the server.

This section contains some of the exceptions that can be encountered when running the IBM WebSphere application server, along with their possible causes and recommended solutions.

Class Not Found Exception
  Cause: The class is not included on the WebSphere application extensions classpath or in the EJB or WAR module.
  Action: Ensure that all required classes are included in the correct location. For more information about classpath locations, see the IBM WebSphere InfoCenter.

Class Not Found Exception
  Cause: The required TopLink JAR files have not been copied into the application extensions classpath.
  Action: Ensure that the `toplink.jar` and `antlr.jar` files are copied into the `<WebSphere install>``\lib\app` directory.

oracle.toplink.exceptions.DatabaseException
  Cause: A TopLink exception has occurred.
  Action: Refer to the specific exception code. The exception code appears in the square brackets in the exception message, such as `[TopLink-1016]`). Exceptions observed here may be exceptions in reading in the properties file, or validation errors due to improper mappings.

  Refer to the Database Exceptions (4002 – 4018) section in the TopLink Exception Reference chapter for detailed information on database exceptions that may occur; refer to the Communication Exceptions (12000 - 12003) section in the TopLink Exception Reference chapter for detailed information on communication exceptions that may occur.

Exception [6066]
  Cause: A bean was created outside of a transaction and then a second bean was created either in or out of a transaction. The exception message returned is:

  `oracle.toplink.exceptions.QueryException: The object <Object> of class <class> with identity hashcode <hashcode> is not from this Unit of Work object space but the parent session's. The object was never registered in this Unit of Work, but read from the parent session and related to an object registered in the Unit of Work. Ensure that you are correctly registering your objects. If you are still having problems, you can use the UnitOfWork.validateObjectSpace() method to help debug where the error occurred. Please see the manual and FAQ for more information.`

  Action: Ensure that all bean creation is performed within the context of a transaction.
  Cause: The bean was not removed during `ejbPassivate` method.
  Action: Ensure that the `ejbPassivate` method removes the bean.
  Cause: A bean-to-object relationship is not privately owned.
  Action: Ensure that all bean-to-object relationships are privately owned.

Exception [7064]
  Cause: An incorrect primary key object is being used with a bean. The exception message returned is:

  `oracle.toplink.exceptions.ValidationException: Exception occurred in reflective EJB bean primary key extraction, please ensure your primary key object is defined correctly: key = 301, bean = <beanName>`

  Action: Ensure that you are using the correct primary key object for a bean.

Exception [7066]
  Cause: An attempt was made to create or remove a bean outside of a transaction. The exception message returned is:

  `oracle.toplink.exceptions.ValidationException: Cannot create or remove beans unless a JTS transaction is present, bean=<bean>`

  Action: Ensure that all removal and creation of beans is performed within a transaction.

Exception [7068]
  Cause: The project class that is specified in the `toplink.properties` file for the session specified on the `toplink_session_name environment` variable cannot be found. The exception message returned is:

  `oracle.toplink.exceptions.ValidationException: The project class` `<projectclass>` `was not found for the` `<toplink_session_name>` `using default class loader.`

  Action: Ensure that the project class provided in the exception is on the IBM WebSphere application server dependent classpath.

Exception [7069]
  Cause: An amendment method was called, but cannot be found. The exception message returned is:

  `oracle.toplink.exceptions.ValidationException: An exception occurred looking up or invoking the project amendment method,` `<amendmentMethod>` `on the class` `<amendmentClass>`;

  Action: Ensure that the required amendment method exists on the class that is specified.

Exception [7070]
  Cause: The `toplink.properties` file cannot be found. The exception message returned is:

  `oracle.toplink.exceptions.ValidationException: A toplink.properties resource bundle must be located on the classpath in a` `TopLink directory.`

  Action: Ensure that the location of the `toplink.properties` file is on the classpath.

Exception [7079]
  Cause: The descriptor that is listed was not found in the session that is specified on the deployment descriptor. The exception message returned is:

  `EXCEPTION DESCRIPTION: The descriptor for [<bean class>] was not found in the session [<session name>]. Check the project being used for this session.`

  Action: Ensure that the project that is specified in the `toplink-ejb-jar.xml` file is the desired project. Also check that the project includes a descriptor for the missing bean class.

Exception [7101]
  Cause: The `toplink-ejb-jar.xml` file was not found. The exception message returned is:

  `No "meta-inf/toplink-ejb-jar.xml" could be found in your classpath. The CMP session could not be read in from file.`

  Action: Ensure that the `toplink-ejb-jar.xml` file is located in the deployed `ejb-jar` file under the `meta-inf` directory.

Exception [9002]
  Cause: The project class that is specified for the session in the `toplink-ejb-jar.xml` file cannot be found. The exception message returned is:

  `EXCEPTION [TOPLINK-9002] (TopLink - X.X.X): oracle.toplink.exceptions.SessionLoaderExceptionEXCEPTION DESCRIPTION: Unable to load Project class [<project class>].`

  Action: Ensure that the project class has been included in the deployed JAR file with the entity beans.

## Problems at Run Time

This section lists some of the common exceptions that can occur at run time when using the TopLink CMP for IBM WebSphere application server.

Exception [6026]
  Cause: A required named query does not exist. The exception message returned is:

  `oracle.toplink.exceptions: Query is not defined`

  Action: Implement the named query. The stack trace of the exception contains the `finder` method that failed.

## Common TopLink for IBM WebSphere Deploy Tool Exceptions

This section lists common exceptions that may occur when running the TopLink for IBM WebSphere application server Deploy Tool.

Class Not Found Exceptions
  Cause: The class that is specified was not found; it is not included on the deploy tool classpath or the system classpath.
  Action: Ensure that all required classes are included on the correct classpath. For more information about classpath setup, see the IBM WebSphere Getting Started document.

  Note: The Deploy Tool calls external IBM classes to generate deployed code. Any exceptions that are thrown from these classes are written to `System.out`. Check Tracing to view the most detailed information.