[jbossts-issues] [JBoss JIRA] Commented: (JBTM-774) TM is not fully OTS spec compliant with respect to XA

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Thu Feb 24 05:55:13 EST 2011

    [ https://issues.jboss.org/browse/JBTM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584363#comment-12584363 ] 

Jonathan Halliday commented on JBTM-774:

Reverting backport to the CP branch as it apparently exposes latent issues in the JBossAS remoting/messaging code.
Fix appears in the 4.6.1.CP branch for CP08-CP10 inclusive, removed prior to CP11.

> TM is not fully OTS spec compliant with respect to XA 
> ------------------------------------------------------
>                 Key: JBTM-774
>                 URL: https://issues.jboss.org/browse/JBTM-774
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JTS
>    Affects Versions: 4.12.0, 4.6.1.CP07
>            Reporter: Michael Musgrove
>            Assignee: Jonathan Halliday
>             Fix For: 4.13.0, 4.6.1.CP08, 4.6.1.CP11
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list