Bug 779121 (SOA-1519)

Summary:	JBPAPP-2893 : Support for crash recovery of tx-inflow with multiple resource managers
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Toshiya Kobayashi <tkobayas>
Component:	EAP	Assignee:	trev <tkirby>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP02
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1519
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Toshiya Kobayashi 2009-10-07 07:57:39 UTC

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.

Comment 1 Toshiya Kobayashi 2009-10-07 07:59:11 UTC

Link: Added: This issue incorporates JBPAPP-2893

Comment 2 Anne-Louise Tangring 2010-02-25 19:02:52 UTC

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.

Comment 5 David Le Sage 2010-03-18 22:29:11 UTC

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.