Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-649

Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue


    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 4.6.1
    • Fix Version/s: 4.6.1.CP04
    • Component/s: Recovery
    • Labels:


      After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test starts to fail. The scenario is:

      1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
      2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
      3. delist res1 and res2 and commit the transaction.
      4. During the commit process, we simulate a failure on res2.commit() so that the res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will throw XAException.XA_RETRY exception – eventually leaving the transaction in a Heuristic state.

      5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and recover the transaction. So we expect that the two sent messages will be received by the receiver. To allow the recovery to happen we give a 60 second timeout to receive the second message. But the result is the first message is received but the second message isn't.

      We know that it is not JTA compliant. But some users may still rely on the old behavior to work.

      Suggestion: a system property can be provided to enable the old behavior if specified by user.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  gaohoward Howard Gao
                  gaohoward Howard Gao
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: