Troubleshooting Known Issues

OC4J XML Parser Dependency

By default, both OC4J and OracleAS TopLink use the OracleAS XML Parser for Java v2. When using OC4J and OracleAS TopLink together, ensure that both use the same version of OracleAS XML Parser for Java v2. Failure to do so may result in XML parsing failures and application errors.

To determine what version of OracleAS XML Parser for Java v2 is used in your OracleAS TopLink installation:

1. Display the comment associated with the <ORACLE_HOME>\lib\xmlparserv2.jar file (where <ORACLE_HOME> is the directory in which you installed OracleAS TopLink).

   1. On Windows, configure WinZip to display comments: select Options > Configuration, select the Miscellaneous tab, and ensure that the Show comments when opening ZIP files check box is checked. Open the <ORACLE_HOME>\lib\xmlparserv2.jar file with WinZip.

   2. On UNIX, use:

      unzip -l <ORACLE_HOME>\lib\xmlparserv2.jar

   The comment shows the build that this version of OracleAS XML Parser for Java v2 belongs to. for example, Label: XDK_MAIN_SOLARIS_031006.

2. Ensure that this build is the same as the build associated with the OracleAS XML Parser for Java v2 used in OC4J.

Using OracleAS TopLink and with BEA WebLogic Application Server, 8.1

When you install OracleAS TopLink in conjunction with the Oracle Application Server 10g Release (10.1.2) installation, changes introduced to the OracleAS XML Parser for Java v2 in 10g Release (10.1.2) can cause issues for users that use OracleAS TopLink 10g Release 2 (10.1.2) in conjunction with BEA WebLogic Application Server, 8.1 (BEA CR136750).

Users will encounter a NoSuchMethodError associated with the constructor of the javax.xml.namespace.QName class. To resolve this problem, users must download the Sun Web Services Development Kit from Sun and place the jax-qname.jar file on their classpath ahead of both the toplink.jar and the weblogic.jar entries.

To download the Sun Web Services Development Kit, go to http://www.sun.com.

IBM WebSphere BMP Example

The duplicate entries of ibm-application*.xmi in bmp.ear cause a Save Failure Exception when deploying the BMP example on IBM WebSphere 5.0.2. To correct this, comment out the following element inside build.ear in the build.xml file:

<metainf dir="${config.dir}">
    <include name="ibm-application*.xmi"/>
</metainf> 

Configuring Examples for RedHat

Running the configureExamples.sh on RedHat Enterprise Server 3.0 may cause a missing class for multipleCopy error. To correct this, modify the build.xml file to contain the absolute path to the toplink_customtasks.jar. For example:

<taskdef name="multipleCopy"
    classname="org.apache.tools.ant.taskdefs.MultipleCopy"
    classpath="<COMPLETE_ABSOLUTE_PATH>/customtasks.jar"/> 

where <COMPLETE_ABSOLUTE_PATH> = /home/iasuser/mwtesting/ant/lib/toplink_customtasks.jar