[
https://issues.jboss.org/browse/WFLY-7282?page=com.atlassian.jira.plugin....
]
Flavia Rainone updated WFLY-7282:
---------------------------------
Description:
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.
was: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.
Steps 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
Double diamond in EJB Transaction
---------------------------------
Key: WFLY-7282
URL:
https://issues.jboss.org/browse/WFLY-7282
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.1.0.Final
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 10.2.0.Final, 11.0.0.Alpha1
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)