[XADISK-156] Response of XAResourceImpl in case of self-initiated rollbacks by XADisk. Created: 02/Dec/13  Updated: 06/Sep/14  Resolved: 06/Sep/14

Status: Resolved
Project: xadisk
Component/s: connector
Affects Version/s: 1.2.2
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Nitin Verma Assignee: Nitin Verma
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Thanks to Alex for bringing this to my attention at thread:


There are some cases when XADisk rolls back its transactions by itself, even in case of a distributed transaction (which is co-ordinated by the transaction-manager[TM]), eg transaction timeout, deadlock detection.

As the TM, being unaware of these rollbacks, would still call, as in general, methods like end, prepare, commit, rollback etc, the XADisk should choose the right mechanism to signal the early self-initiated rollback to the TM. There is an error code of XA_RB* (in XAException), can XADisk employ these error codes?

Comment by Nitin Verma [ 06/Sep/14 ]

During any kind of rollback, whether application initiated or xadisk initiated (eg timeout), the cleanup process for the rollback removes the information of the transaction/session from the xadisk in-memory data-structure. Keeping this information after rollback (and it is not clear for how long this information should be kept) is not straighforward in the current design/implementation. So, closing this bug.

Generated at Sat Dec 10 03:05:03 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.