]
Ondra Chaloupka moved JBEAP-5546 to WFLY-6920:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6920 (was: JBEAP-5546)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
IIOP
(was: EJB)
(was: IIOP)
Affects Version/s: 10.1.0.CR1
(was: 7.1.0.DR1)
Enhance behavior of transaction propagation called over IIOP to not
start 2PC when called ejb creates own new transaction
-------------------------------------------------------------------------------------------------------------------------
Key: WFLY-6920
URL:
https://issues.jboss.org/browse/WFLY-6920
Project: WildFly
Issue Type: Enhancement
Components: EJB, IIOP
Affects Versions: 10.1.0.CR1
Reporter: Ondra Chaloupka
Assignee: Tomasz Adamski
Priority: Minor
Based on discussion at jira JBEAP-5126
(
https://issues.jboss.org/browse/JBEAP-5126?focusedCommentId=13271878#comm...)
there could be a good enhancement for transaction propagated over ejb called over iiop to
not start 2PC process when the called ejb creates its own new transaction
({{TransactionAttributeType.REQUIRES_NEW}}).
Quoting Tom's comment here
{quote}
Yeah, its expected to be this way for JTS as the context is propagated
over. It could be possible to register an enhancement in the iiop
subsystem to remove the context from the thread if the EJB does not
require a propagated transaction.
{quote}