Bug 1411288
| Summary: | [GSS](6.4.z) Deadlock in BasicAction when jboss remoting and JTA is used | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Tom Ross <tom.ross> |
| Component: | EJB | Assignee: | Fedor Gavrilov <fgavrilo> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan Martiska <jmartisk> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.7 | CC: | bmaxwell, david.lloyd, fgavrilo |
| Target Milestone: | --- | ||
| Target Release: | EAP 6.4.13 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-16 15:45:53 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: | |||
Closing as this was fixed in EAP 6.4 CP13, so this is a duplicate of another one possibly: https://bugzilla.redhat.com/show_bug.cgi?id=1378396 |
At EJBRemoteTransactionPropagatingInterceptor, a transaction that has been already open at current server could be ignored, thus causing the transaction to be reimported, resulting in the double diamond problem. To reproduce you need a reinvocation at a server that was already participating in the transaction, as the scenario below for example: server1 -> server2 -> server1