4 Administering the JMS Resource Adapter on Oracle GlassFish Server

Note following configuration information and considerations to bear in mind when deploying the JMS resource adapter on :

• Oracle recommends using the Java Connector Architecture container to provide methods to set credentials using secure methods.

  See Securing JMS Resource Adapter Connections.

• supports lazy connection enlistment. See Lazy Enlistment of Connections in a Transaction.

• The Glassfish XAResource timeout value is 30 seconds by default and is independent of the transaction timeout. If you require a longer XAResource timeout, you must set the Glassfish system property server-config.transaction-service.property.xaresource-txn-timeout to a value equal to your transaction timeout value.

• Oracle GlassFish 3.1.x has a known issue regarding how outbound message-driven bean (MDB) connections remain associated with a rolled back transaction.

  You may receive a javax.transaction.xa.XAException: The resource already has an active association with a transaction exception if your application uses the javax.ejb.MessageDrivenContext.setRollbackOnly method within an XA enabled MDB's onMessage method, which in turns uses an XA backed outbound connection factory. This exception is thrown after a rollback and the associated connection is taken from the connection pool to be reused in another transaction. If you have a licensed version of Oracle GlassFish, contact your Oracle Glassfish Support representative. If you have an open source version, a patch is available at https://github.com/javaee/glassfish/issues/19094.

• You may receive a ClassNotFoundException exception when deploying the JMS resource adapter on a Glassfish 3.1 cluster environment. If this happens, copy the wlthint3client.jar file that is packaged in the wljmsra.rar file to the <Glassfish_install_dir>/lib directory. See https://github.com/javaee/glassfish/issues/19111.

• You may receive the following exception if you undeploy and redeploy a WAR file multiple times.

  Failed to generate class for weblogic.messaging.dispatcher.FastDispatcherImpl_12120_WLStub

  The workaround for this exception is to restart the GlassFish server.

• See Oracle GlassFish Server 3.1.2 and 3.1.2.2 Release Notes in the Oracle GlassFish Server Release Notes for a summary of new product features in the 3.1.2 and 3.1.2.2 releases, and descriptions and workarounds for known issues and limitations.