Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-3932

JmsConnectionPool reverts to non-xa when transaction has expired

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.10 CP1
    • Fix Version/s: 4.11 CP3
    • Component/s: Transports
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tcunning Thomas Cunningham
                  Reporter:
                  kconner Kevin Conner
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: