Skip Headers

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

Previous | Next |

# Common BEA WebLogic Server Deployment Exceptions

The following are some of the most common exceptions that are encountered when you deploy entity beans to a BEA WebLogic Server.

For more information about specific versions, see the following:

- Common BEA WebLogic Server 6.1 Exceptions,

- Common BEA WebLogic 7.0 Exceptions,

- Common BEA WebLogic 8.1 Exceptions,

Assertion Error
  Cause: This exception occurs if the `toplink.jar` file is not properly set on your classpath. The exception message returned is:

  `weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Could not load class '``oracle.toplink``.internal.ejb.cmp.wls.WlsCMPDeployer': java.lang.ClassNotFoundException:` `oracle.toplink``.internal.ejb.cmp.wls.WlsCMPDeployer` `ERROR: ejbc found errors`

  Action: Ensure the <`ORACLE_HOME>``/toplink/jlib/toplink.jar` file is specified on your system classpath.

Error Deploying Application
  Cause: A DeploymentException has occurred.
  Action: Refer to the specific error code. The error code appears in the square brackets in the exception message, such as `[TopLink-8001]`). These errors may refer to errors in the specification of the project location reading in the properties file or validation errors due to improper mappings.

Exception 8001
  Cause: This error occurs if the TopLink project file is not specified in the `toplink-ejb-jar.xml` file. The exception message returned is:

  `<Error> <J2EE> <Error deploying application Account:``Unable to deploy EJB: AccountBean from Account.jar:``LOCAL EXCEPTION STACK:``EXCEPTION [TOPLINK-8001] (TopLink (WLS CMP) - X.X.X): oracle.toplink.ejb.DeploymentException` `EXCEPTION DESCRIPTION: No` TopLink `project was specified for this bean.` `at` `oracle.toplink.ejb.DeploymentException.noPro jectSpecified(DeploymentException.java:132) at oracle.toplink.internal.ejb.cmp.ProjectDeployment.readProject(ProjectDeployment.java:378)`

  Action: Ensure there is an entry in the `toplink-ejb-jar.xml` file for either the `project-xml` or `project-class`.

Exception 8016
  Cause: This exception can occur if the location of the TopLink project file for the bean is not properly specified. The exception message returned is:

  `<Error> <J2EE> <Error deploying application Account:``Unable to deploy EJB: AccountBean from Account.jar:``LOCAL EXCEPTION STACK:``EXCEPTION [TOPLINK-8016] (TopLink (WLS CMP) - X.X.X): oracle.toplink.ejb.DeploymentException` `EXCEPTION DESCRIPTION: An error occurred while setting up the project: [java.io.FileNotFoundException: Account.xml]``INTERNAL EXCEPTION: java.io.FileNotFoundException: Account.xml` `at` `oracle.toplink.ejb.DeploymentException.errorCreatingProject(Unknown Source)`

  Action: Check the file name as it is specified in the `toplink-ejb-jar.xml` file, and the location of the project file on the file system.

Cannot Start Up Connection Pool
  Cause: An exception has occurred while setting up the connection pool. The exception message returned is:

  `<Error> <JDBC> <Cannot startup connection pool "ejbPool" weblogic.common.ResourceException: Cannot load driver class: org.hsqldb.jdbcDriver>``...`

  Action: Check the nested SQL exception to determine the cause of the exception. Typical reasons for this include:

  - The JDBC driver is not on the classpath.

  - The user name or password provided by the user is incorrect.

  - The server URL or driver name is not properly specified.

  Please consult the BEA WebLogic Server documentation and your JDBC driver documentation for help on the specific exception raised by BEA WebLogic.

Error Message
  Cause: This problem occurs if you are using the GA version of BEA WebLogic Server 6.0. The exception message returned is:

  `weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Could not create an instance of class 'null': java.lang.NullPointerException` `at java.lang.Class.forName0(Native Method)` `at java.lang.Class.forName(Class.java:120)` `at weblogic.ejb20.persistence.PersistenceType. loadClass` (PersistenceType.java:309)

  Action: Upgrade to WebLogic Server 6.0 (Service Pack 1) or a higher release.

EJBC Found Errors
  Cause: This error occurs if the `toplink.jar` file is not properly set on your classpath. The exception message returned is:

  `ERROR: ejbc found errors` `Error from ejbc: Error while loading persistence resource TopLink_CMP_Descriptor.xml Make sure that the persistence type is in your classpath.`

  Action: Ensure the `<ORACLE_HOME>``/toplink/jlib/toplink.jar` file is specified on your system classpath.

EJB Deployment Exception
  Cause: This exception occurs if the location of the TopLink project file for the bean is not properly specified. The exception message returned is:

  `weblogic.ejb20.EJBDeploymentException: Error Deploying CMP EJB:; nested exception is: weblogic.ejb20.cmp.rdbms.RDBMSException: An error occurred setting up the project:` `EXCEPTION [TOPLINK-13000] (vX.X [TopLink for WebLogic X.X] JDK1.2): oracle.toplink.xml.XMLDataStoreException` EXCEPTION DESCRIPTION: File not found...

  Action: Check the file name as it is specified in the `toplink-ejb-jar.xml` file, and the location of the TopLink project file on the file system.

Deploying EJB Component
  Cause: A typical cause of this exception is that the `toplink-ejb-jar.xml` file is referring to a local DTD file using a file name or location that is incorrect. The exception message returned is:

  `Error deploying EJB Component:... weblogic.ejb20.EJBDeploymentException: Exception in EJB Deployment; nested exception is:` `Error while deploying bean..., File... Not Found at weblogic.ejb20.persistence.PersistenceType.setup Deployer(PersistenceType.java:273)`

  Action: Ensure that all XML files refer to valid DTD files and locations.

Cannot Start Up Connection Pool ejbPool
  Cause: This exception is raised to indicate that an error has occurred while setting up the connection pool. The exception message returned is:

  `Cannot startup connection pool "ejbPool" weblogic.common.ResourceException:` `Could not create pool connection. The DBMS driver exception was:...`

  Action: Check the nested SQL exception to determine the cause of the error. Typical problems include:

  - The driver is not on the classpath.

  - The user name or password is incorrect.

  - The server URL or driver name is not properly specified.

  Please consult the BEA WebLogic Server documentation and your JDBC driver documentation for help on the specific exception raised by BEA WebLogic.

Other Exceptions

Occasionally, changes made to the server's configuration file (`config.xml`) do not appear to be applied when the server is restarted. If this occurs, try removing the temporary directories created by BEA WebLogic Server. You can find them under the `wlserver6.1` directory, at the same level as the `config` directory.