12 Oracle Containers for J2EE

12.1 Accessing WebLogic Server Resources

OC4J server clients or remote clients can connect to a WebLogic server in order to access resources such as EJBs. These types of scenarios require the wlthint3client.jar library. The JAR is available for download from https://metalink.oracle.com (My Oracle Support). The JAR must be included on the classpath of your client. For detailed instructions on how to access WebLogic server resources, see "Accessing WebLogic Server Resources" in the Oracle Containers for J2EE Services Guide.

12.2 JMS Interoperability with WLS

Performance and/or classpath issues may arise when OC4J server clients use the ContextScanningResourceProvider resource provider to access WebLogic server JMS destinations. To work around this issue, use the resource.names property to explicitly set a comma-separated list (without spaces) of JNDI names for the JMS resources that are required from the external server. If the property is not set, the ContextScanningResourceProvider resource provider's default behavior is to scan the entire JNDI tree of a given external server in order to detect all Java EE resources that can be mapped into an OC4J instance.

The following example demonstrates setting the resource.names property in the orion-application.xml file. The resource.names property is set to TopicOne,QueueOne,TopicTwo. This value represents a list of JNDI names for JMS destinations that the ContextScanningResourceProvider resource provider attempts to lookup from the external WebLogic server.

<resource-provider
   class="com.evermind.server.deployment.ContextScanningResourceProvider"
   name="WebLogicRP">
   <property name="java.naming.factory.initial"
      value="weblogic.jndi.WLInitialContextFactory"/>
   <property name="java.naming.provider.url" value="t3://localhost:7001/"/>
   <property name="java.naming.security.principal" value="user_name"/>
   <property name="java.naming.security.credentials" value="user_password"/>
   ...

   <!-- configure the set of known JMS destinations that are required for
   this application -->

   <property name="resource.names" value="TopicOne,QueueOne,TopicTwo"/>
   ...
</resource-provider>

For more information on using the ContextScanningResourceProvider resource provider to access third-party JMS destinations, see the Oracle Containers for J2EE Services Guide.

12.3 Deploying Custom Login Modules With Multiple JVMS

When deploying a custom login module and multiple JVMs are configured, the login module is only configured and recognized for one of the JVMs during deployment. This results in an authentication error for any requests that are routed to the other JVMs.To workaround this issue, restart the OC4J instance after deployment in order for the JVMs to pick up the correct configuration.

12.4 Applications Share HTTP Client Static Memory

The HTTP Client library is loaded by the OC4J system class loader and is therefore inherited by all applications deployed in the OC4J instance. As a result, the HTTP Client's static memory is shared across all applications. An application that modifies default values that are stored in the HTTP Client's static memory may affect other applications that also rely on the HTTP Client library.The work around for this issue is to have each application import a local copy of the HTTP Client library. The HTTP Client's static memory is then private to the application and cannot be modified by another application.

The following example demonstrates how to configure an application to import a local copy of the HTTP Client library and not inherit the HTTP Client library loaded by the OC4J system class loader. The change must be made in an application's orion-application.xml file.

<orion-application>
   ...
   <imported-shared-libraries>
      <remove-inherited name="oracle.http.client">
   </imported-shared-libraries>
   ...
   <library path="ORACLE_HOME/j2ee/home/lib/http_client.jar"/>
   ...
</orion-application>

12.5 Exception When Using the In-Database Coordinator

A null pointer exception occurs when a resource is enlisted in a transaction and the transaction manager is configured to use the in-database coordinator.

12.6 JAZNMigration Tool Does Not Migrate ADFPrincipal Type Correctly

Be aware of the following issue when you use the OracleAS JAAS Provider migration tool to migrate policies from the file-based provider to the Oracle Identity Management (essentially, Oracle Internet Directory) security provider, either in policy mode or all mode: The migration tool prepends the Oracle Internet Directory realm name to custom or nonrealm principal names in grantee entries in the policy configuration. (A custom principal may come into play when authenticating through a custom login module, for example.)

In the migrated configuration, a custom principal name in a grantee entry becomes, for example, us/anyone instead of just anyone, assuming us is the realm name. This results in permission issues. For ADF applications, for example, this results in public pages not working after migration to Oracle Internet Directory as the security provider.

The following workarounds are available for this issue:

• Manually remove the us/ prefix from the LDIF file that the migration tool creates, prior to importing it into Oracle Internet Directory.

• Manually remove the us/ prefix from relevant grantee entries after the migration, using Oracle Internet Directory administration tools.

12.7 Configuration Issues When Using an External LDAP Provider

If you plan to use an external LDAP provider for an application, it is recommended that you use a middle tier installation that is configured with the default XML security provider.

If you have a middle tier installation that is associated with an infrastructure installation (such as OID) and you want to use an external LDAP provider, you need to manually edit the jazn.xml file. Change the provider and location attributes of the <jazn> element as follows:

<jazn provider="XML" location="./system-jazn-data.xml" ... >

12.8 For AIX and Linux on POWER: Process Does Not Start With JDK 1.4.2

When you replace JDK 1.5 with JDK 1.4.2, OC4J does not start and the OPMN log (ORACLE_HOME/opmn/logs//default_group~home~default_group~1.log) gives an error similar to the following:

--------
Start process
--------
**************************** WARNING ******************************
You are currently running with data limits not set to unlimited.
You may experience out of memory(OOM) conditions.
In the event of an OOM error, please increase the data limit value.
You may use "ulimit -d unlimited" to set data limit as unlimited.
*******************************************************************
 
[ Unrecognized option:
-Xjit:exclude={oracle/sysman/emSDK/eml/util/iAS/IASLogConfig.getViewLogsURL(Ljav
ax/servlet/ServletContext;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/
http/HttpServletResponse;)Ljava/lang/String;},
exclude={oracle/security/jazn/util/OHSH.update([B)V},
exclude={com/phaos/ASN1/ASN1Sequence.<init>(Ljava/io/InputStream;)V},
exclude={com/phaos/crypto/DES.l([B[IZ)V} ]
[ JVMCI123: Unable to parse 1.2 format supplied options - rc=-6 ]
Could not create JVM.

Use the following workaround to ensure that OC4J starts with JDK 1.4.2:

1. Remove the following lines from opmn.xml ($ORACLE_HOME/opmn/conf/opmn.xml):

   -Xjit:exclude={oracle/sysman/emSDK/eml/util/iAS/IASLogConfig.getViewLogsURL(
   Ljavax/servlet/ServletContext;Ljavax/servlet/http/HttpServletRequest;Ljavax/s
   ervlet/http/HttpServletResponse;)Ljava/lang/String;},
   exclude={oracle/security/jazn/util/OHSH.update([B)V},
   exclude={com/phaos/ASN1/ASN1Sequence.<init>(Ljava/io/InputStream;)V},
   exclude={com/phaos/crypto/DES.l([B[IZ)V}
   

2. Start the OC4J instance by using the following command:

   opmnctl startall
   

12.9 For HP-UX and Solaris Operating System (x86) Only: OC4J Process Does Not Start With JDK 1.4.2 or JDK 1.6

When you replace JDK 1.5 with JDK 1.4.2 or JDK 1.6, OC4J does not start and the OPMN log (ORACLE_HOME/opmn/logs//default_group~home~default_group~1.log ) gives an error similar to the following:

--------
Start process
--------
Unrecognized VM option 'AppendRatio=3'
Could not create the Java virtual machine.

Use the following workaround to ensure that OC4J starts:

1. Shut down the OC4J instance by using the following command:

   opmnctl stopall
   

2. Remove the following lines from opmn.xml ($ORACLE_HOME/opmn/conf/opmn.xml):

   AppendRatio=3
   

3. Start the OC4J instance by using the following command:

   opmnctl startall
   

12.10 For HP-UX PA-RISC (64-Bit): Attempts to Run JAZN Migration Tool with JDK 1.6 Fails

While using JDK 1.6 with Oracle Application Server 10g Release (10.1.3.5), JAZN Migration Tool fails.

Before running JAZN Migration Tool on JDK 1.6, you must set the environment variable, SHLIB_PATH, by using the following command:

export SHLIB_PATH=$ORACLE_HOME/jdk/jre/lib/PA_RISC2.0/jli

12.11 New Features

This section describes the new features for Oracle Containers for J2EE. This section includes the following topics:

• Section 12.11.1, "Peek OC4J Runtime Inspector Utility"

• Section 12.11.2, "New Administration Commands"

• Section 12.11.3, "Exploded-Directory Deployment"

• Section 12.11.4, "MBean Support For the oracle.j2ee.jms Implementation"

• Section 12.11.5, "Documentation Updates"

12.12 Documentation Errata

The following errors appear in the OC4J Documentation:

• Wrong WebLogic Server Interoperability JAR Name