Bug 1096947
| Summary: | [GSS] (6.2.4) JBTM-1702: one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | jolee | |
| Component: | Transaction Manager | Assignee: | Emmanuel Hugonnet (ehsavoie) <ehugonne> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondrej Chaloupka <ochaloup> | |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | |
| Priority: | unspecified | |||
| Version: | 6.2.0 | CC: | bmaxwell, cdewolf, ehugonne, jawilson, jolee, smumford | |
| Target Milestone: | CR1 | |||
| Target Release: | EAP 6.2.4 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
In previous versions of JBoss EAP 6, it was found that XAExceptions thrown by XAResource were being swallowed and that bean invocation was falsely appearing to succeed.
The issue presented when one-phase optimization was in use and the `XAResource.end()` method threw an `XA_RBCOMMFAIL` error. The bean client would seem to complete the bean method invocation successfully, however the transaction would have been rolled back by the database causing any subsequent bean invocations to fail as data assumed to be stored was not available.
In this release, if the transaction fails in the XAResource, it is still rolled back, however an exception is now thrown so that the calling code can detect an error instead of assuming a success.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1107569 (view as bug list) | Environment: | ||
| Last Closed: | 2014-08-07 12:12:39 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: | 1107569 | |||
| Bug Blocks: | 1067534, 1105419 | |||
|
Description
jolee
2014-05-12 18:32:03 UTC
repo: ssh://code.engineering.redhat.com/narayana.git branch: remotes/engineering/4.17.15.Final-redhat-JBTM-1702 Created a tag (4.17.15.Final-redhat-eap-6.2.3) [1] to be used for the component upgrade. Note that if another backport is identified, this tag will need to be deleted and recreated to reflect the new inclusive commit. [1] [jolee@jolee narayana]$ git push engineering 4.17.15.Final-redhat-eap-6.2.3 Counting objects: 1, done. Writing objects: 100% (1/1), 185 bytes | 0 bytes/s, done. Total 1 (delta 0), reused 0 (delta 0) remote: Updating references: 100% (1/1) To ssh://code.engineering.redhat.com/narayana.git * [new tag] 4.17.15.Final-redhat-eap-6.2.3 -> 4.17.15.Final-redhat-eap-6.2.3 Not in 4.17.15.Final-redhat-4 thus requires a component upgrade Verified for EAP 6.2.4.CP.CR1. Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1702 to Closed Christian von Kutzleben <christian.vonkutzleben> updated the status of jira JBTM-1702 to Reopened Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1702 to Closed Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1702 to Reopened Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1702 to Closed |