Bug 1329142 - [GSS](6.4.z) Throw XAException in XATerminator::commit if a wrapped resource fails transiently
Summary: [GSS](6.4.z) Throw XAException in XATerminator::commit if a wrapped resource ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager
Version: 6.4.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: CR1
: EAP 6.4.9
Assignee: Radovan Netuka
QA Contact: Ondrej Chaloupka
URL:
Whiteboard:
Depends On:
Blocks: eap649-payload 1325725
TreeView+ depends on / blocked
 
Reported: 2016-04-21 09:44 UTC by Tom Ross
Modified: 2019-11-14 07:50 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:57:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-2357 0 Critical Closed Throw XAException in XATerminator::commit if a wrapped resource fails transiently 2017-03-22 13:22:01 UTC
Red Hat Issue Tracker JBTM-2579 0 Critical Closed Throw XAException in XATerminator::commit if a wrapped resource fails transiently 2017-03-22 13:22:00 UTC
Red Hat Knowledge Base (Article) 2434981 0 None None None 2016-07-11 07:21:12 UTC

Description Tom Ross 2016-04-21 09:44:53 UTC 
It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome.
The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan.
Add Link
Comment 1 Radovan Netuka 2016-05-23 08:40:14 UTC 
This should already be fixed in JBoss Transaction Manager 4.17.31. See linked JBTM issue for details.
Comment 2 JBoss JIRA Server 2016-06-14 11:38:09 UTC 
Jiri Pallich <jpallich> updated the status of jira JBEAP-2357 to Closed
Comment 3 Jiří Bílek 2016-06-30 09:33:43 UTC 
Verified with EAP 6.4.9.CP.CR2
Comment 4 Petr Penicka 2017-01-17 12:57:43 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 5 Petr Penicka 2017-01-17 12:58:23 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.