]
Scott Marlow closed WFLY-10225.
-------------------------------
Resolution: Rejected
Our internal testing is passing now, so we do not need this fix.
Possible problem inflowing transactions from IIOP
-------------------------------------------------
Key: WFLY-10225
URL:
https://issues.jboss.org/browse/WFLY-10225
Project: WildFly
Issue Type: Bug
Components: EJB, IIOP, Transactions
Reporter: David Lloyd
WFLY-7680 introduced the concept of lazy transaction inflow. The transaction is not
associated with the thread unless the EJB invocation mode causes the caller transaction to
be used (if present).
This may have caused a problem where transaction association does not function correctly
when transactional operations are invoked via IIOP, though I do not have a good
explanation as to why this would happen yet.
The significant participants in this process appear to be:
* {{org.jboss.as.ejb3.iiop.EjbCorbaServant}}
* {{org.jboss.as.ejb3.iiop.EjbIIOPTransactionInterceptor}}
* {{org.jboss.as.ejb3.tx.CMTTxInterceptor}}
It's possible that there is some situation where the behavior of the invocation has
changed due to the remote TX inflow interceptor being gone, which prevents the transaction
from being associated with the thread until later than before. Or, this may all be a
coincidence and the problem may be caused elsewhere.