[
https://jira.jboss.org/browse/JBTM-578?page=com.atlassian.jira.plugin.sys...
]
Michael Musgrove commented on JBTM-578:
---------------------------------------
JBTM-577 is about the OTS transaction id (the otid) not encoding the global transaction id
correctly (see the method Utility.otidToUid) which was a problem for BlackTie.
This JIRA is about ignoring the bqal component of the otid.
The fix for JBTM-577 added a comment saying that "THIS WILL BE AN ISSUE FOR
INTEROPERABILITY!!" and JBTM-578 was raised to track it.
However, the interoperability is only for TM implementations that provide integration with
C XA Resource Managers as described in Annex B.2.5 of the OTS specification but JBossTS
does not implement this appendix (it uses JTA as the preferred XA integration mechanism).
Furthermore, in OTS, the bqual field is intended for applications where different
processes wish to share the same (XA) transaction branch (referred to as the
tightly-coupled model). BlackTie is the primary use case for C XA integration but it uses
the loosely coupled model (note also that interoperability via OSI-TP with other TP
systems does NOT support the tightly-coupled model).
Consequently, I recommend closing this JIRA as will not fix.
Put back branch equivalent code for ArjunaCore transactions
-----------------------------------------------------------
Key: JBTM-578
URL:
https://jira.jboss.org/browse/JBTM-578
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transaction Core
Affects Versions: 4.7.0
Reporter: Mark Little
Assignee: Michael Musgrove
Fix For: future
Needed for interop.
--
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