Bug 1329142

Summary: [GSS](6.4.z) Throw XAException in XATerminator::commit if a wrapped resource fails transiently
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tom Ross <tom.ross>
Component: Transaction ManagerAssignee: Radovan Netuka <rnetuka>
Status: CLOSED CURRENTRELEASE QA Contact: Ondrej Chaloupka <ochaloup>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.4.5CC: bmaxwell, cdewolf, jbilek, jtruhlar, rnetuka, tom.jenkinson
Target Milestone: CR1   
Target Release: EAP 6.4.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 12:57:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1324262, 1325725    

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.