Hide Forgot
Affects: Release Notes Date of First Response: 2010-02-25 14:02:52 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/321874 project_key: SOA JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs. In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid.
Link: Added: This issue incorporates JBPAPP-2893
Approved, but not required, for SOA 4.3 CP03. It will only be included if it is fixed in the EAP version this release will pick up.
Documented as Known Issue in Release Notes: https://jira.jboss.org/jira/browse/JBPAPP-2893 There are problems with crash recovery when inflowing transactions are associated with multiple resource managers. As a consequence, a single XAResource can no longer be returned to drive the recovery for a given Xid. There is currently no work-around solution for this problem.