22.13 Troubleshooting and Verifying the Deployment

After you deploy your application, test it to ensure that it runs correctly on the target application server. This section provides some common troubleshooting tips.

Section 22.13.1, ""Class Not Found" or "Method Not Found" Errors"
Section 22.13.2, "Application Is Not Using data-sources.xml File on Target Application Server"
Section 22.13.3, "Using jazn-data.xml with the Embedded OC4J Server"
Section 22.13.4, "Error "JBO-30003: The application pool failed to check out an application module due to the following exception""

22.13.1 "Class Not Found" or "Method Not Found" Errors

Problem

You get "Class Not Found" or "Method Not Found" errors during runtime.

Solution

Check that ADF runtime libraries are installed on the target application server, and that the libraries are at the correct version.

You can use the ADF Runtime Installer wizard in JDeveloper to check the version of the ADF runtime libraries. To launch the wizard, choose Tools > ADF Runtime Installer > Application_Server_Type. Application_Server_Type is the type of the target application server (for example, WebLogic, JBoss, or standalone OC4J).

22.13.2 Application Is Not Using data-sources.xml File on Target Application Server

Problem

After deploying and running your application, you find that your application is using the data-sources.xml file that is packaged in the application's EAR file, instead of using the data-sources.xml file on the target application server. You want the application to use the data-sources.xml file on the target application server.

Solution

When you create your EAR file in JDeveloper, choose not to include the data-sources.xml file. To do this:

Choose Tools > Preferences to display the Preferences dialog.
Select Deployment on the left side.
Deselect "Bundle Default data-sources.xml During Deployment".
Click OK.
Re-create the EAR file.

Before redeploying your application, undeploy your old application and ensure that the data-sources.xml file on the target application server contains the appropriate entries needed by your application.

22.13.3 Using jazn-data.xml with the Embedded OC4J Server

If your application uses jazn-data.xml, you should be aware of how the embedded OC4J server uses this file: If the embedded OC4J server finds a jazn-data.xml file in the application's META-INF directory, then the embedded OC4J server will use it. The embedded OC4J server will also set the <workspace>-oc4j-app.xml file to point to this jazn-data.xml file. This enables you to edit the jazn-data.xml file using the Embedded OC4J Server Preferences dialog.

If there is no jazn-data.xml file in META-INF, the embedded OC4J server will create a <workspace>-jazn-data.xml file in the workspace root. You would then have to go and edit that file (or use the Embedded OC4J Server Preferences dialog to do so).

22.13.4 Error "JBO-30003: The application pool failed to check out an application module due to the following exception"

Problem

You get the following error in the error log:

05/11/07 18:12:59.67 10.1.3.0.0 Started
05/11/07 18:13:05.687 id: 10.1.3.0.0 Started
05/11/07 18:13:38.224 id: Servlet error
JBO-30003: The application pool (<class_name>) failed to checkout an application
 module due to the following exception:
oracle.jbo.JboException: JBO-29000: Unexpected exception caught:
oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught:
oracle.classloader.util.AnnotatedClassFormatError, msg=<classname> (Unsupported
 major.minor version 49.0)

      Invalid class: <classname>
             Loader: webapp5.web.id:0.0.0
        Code-Source: /C:/oc4j/j2ee/home/applications/webapp5/webapp5/WEB-INF/classes/
      Configuration: WEB-INF/classes/ in C:\oc4j\j2ee\home\applications\webapp5\webapp5\WEB-INF\classes
 
    Dependent class: oracle.jbo.common.java2.JDK2ClassLoader
             Loader: adf.oracle.domain:10.1.3
        Code-Source: /C:/oc4j/BC4J/lib/adfm.jar
      Configuration: <code-source> in /C:/oc4j/j2ee/home/config/server.xml

    at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1892)

Solution

A possible cause of this exception is that the application was unable to connect to the database for its data bindings. Check that you have set up the required database connections in your target application server environment, and that the connections are working.