Resource References JDBC Connection Utilization Oracle RAC Support Debugging

7-10 Configuring and Managing JMS for Oracle WebLogic Server

7.3.3 Resource References

If you choose to use the resource references and the resource type is javax.jms.XXXConnectionFactory, WebLogic wraps the AQ JMS objects passed to a user application. If you also use the AQ JMS extension APIs, they must be unwrapped as described in Section 7.3.2, AQ JMS Extensions. WebLogic resource reference wrappers do not automatically pool AQ JMS connections. Instead, AQ JMS server-side integration depends on data source connection pooling to mitigate the overhead of opening and closing JMS connections and sessions. WebLogic resource references disable pooling because the AQ JMS provider JMS connection factory is always pre-configured with a client identifier, which in turn, causes WebLogic resource references to disable its pooling feature.

7.3.4 JDBC Connection Utilization

An AQ JMS session holds a JDBC connection until the JMS session is closed, regardless of whether the connection uses a data source or a JDBC URL. Oracle recommends that you close an AQ JMS session if the session becomes idle for an extended period of time. Closing the JMS session releases the JDBC connection back to the WebLogic data source pool see Section 7.2.2.1.1, Data Source Tuning or releases the database and network resources for a JDBC URL.

7.3.5 Oracle RAC Support

The following section provides information on limitations in Oracle RAC environments: ■ Oracle RAC environments require the configuration of WebLogic Multi Data Sources to provide AQ JMS Oracle RAC failover. See Using WebLogic Server with Oracle RAC in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server. ■ Oracle RAC failover is not supported when using a WebLogic AQ JMS stand-alone client for this release.

7.3.6 Debugging

To use AQ JMS tracing and debugging, set the following system property: oracle.jms.traceLevel. The value of this property is an integer ranging from 1 to 6 where a setting of 6 provides the finest level of detail. The trace output is directed to the standard output of the running JVM.

7.3.7 Performance Considerations