JmsConnectionPool reverts to non-xa when transaction has expired ---------------------------------------------------------------- Key: JBESB-3932 URL: https://issues.jboss.org/browse/JBESB-3932 Project: JBoss ESB Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Transports Affects Versions: 4.10 CP1 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.11 CP3 Attachments: JBESB-3932.diff The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API. The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.