TM is not fully OTS spec compliant with respect to XA ------------------------------------------------------ Key: JBTM-774 URL: https://jira.jboss.org/browse/JBTM-774 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1.CP07, 4.12.0 Reporter: Michael Musgrove Assignee: Mark Little Fix For: 4.13.0, 4.6.1.CP08 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira