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

TM is not fully OTS spec compliant with respect to XA

    Details

    • Steps to Reproduce:
      Hide

      Start a JTS transaction with a timeout. After the timeout has expired and after a sweep of the Transaction Reaper has marked the transaction as aborted try to obtain the propagation context from the CosTransactions::Coordinator CORBA object. The invocation will raise the Unavailable exception.

      Show
      Start a JTS transaction with a timeout. After the timeout has expired and after a sweep of the Transaction Reaper has marked the transaction as aborted try to obtain the propagation context from the CosTransactions::Coordinator CORBA object. The invocation will raise the Unavailable exception.

      Description

      According to the OTS specification the Propagation Context should always be available. Annex B2.2 says:

      "The Transaction Service does not restrict the availability of the PropagationContext: the operation get_txcontext on the Coordinator never raises Unavailable."

      However the TM is raising this exception if the transaction has been aborted (for example if the reaper has detected that the transaction has timed out). [The method ArjunaTransactionImple.get_txcontext will always raise CosTransactions.Unavailable if the transaction is not active.]

      This problem was observed whilst running the BlackTie test suite.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jhalliday Jonathan Halliday
                  Reporter:
                  mmusgrov Michael Musgrove
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: