Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Not A Problem
-
1.2, 1.4, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4
-
None
Description
Under high concurrent use, the eviction thread can temper with an in-use object from the pool, potentially causing catastrophic results, as illustrate in the below log from our use. Note the object - in our case JMSSession is closed in-flight (after message send but before commit), causing the commit to fail with javax.jms.IllegalStateException: MQJMS1024: session closed error.
2009-10-12 15:08:40,254 DEBUG [asyncDelivery59] Borrowed session com.ibm.mq.jms.MQQueueSession@40bc88 for jms connector 2009-10-12 15:08:40,341 DEBUG [Timer-0] Physically closing com.ibm.mq.jms.MQQueueSession@40bc88 for connector 2009-10-12 15:08:40,669 DEBUG [asyncDelivery59] Returning session com.ibm.mq.jms.MQQueueSession@40bc88 for jms conn ector 2009-10-12 15:08:40,433 ERROR [asyncDelivery59] Exception caught while committing transaction [com.ibm.mq.jms.MQQueueSession@40bc88]