JMS Wrapper Session Pool is Being Closed Due to Transaction Timeout Caused by Foreign Resource Manager
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.6 to 184.108.40.206.0
Information in this document applies to any platform.
In a WebLogic Server domain, with J2EE applications configured to use a foreign JMS provider such as IBM MQ Series and sometimes when working with JMS Wrappers, the JMS session pool is being closed when the XA call fails due to the transaction (TX) being marked for rollback only due to timeout. This is not an acceptable call because the entire pool has not necessarily turned bad. User will see JMSSessionPoolTester.onException causing session pool close when XA error happened due to TX timeout resulted as runtime/system exception:
Note: Here the transaction is not only rolled back but also JMSSessionPoolTester.onException is called so that the JMS Pool is closed, although there was no problem with the pool.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms