Description of problem: If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation: WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive This is only the case if other resources are involved, i.e. a DB via JPA. If a simple bean is used (like ejb-remote quickstart) this warning is not shown. It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked. How reproducible: With transactional EJB's which are using other Tx resources. Worse case if a SFSB with a @Remote method is used Steps to Reproduce: See WFLY-3801 Actual results: arjuna WARN messages SFSB remove ERROR
Hi, I removed "Transaction Manager" from this as I don't believe its a TM issue. As discussed on the thread I think EJB should not be trying to access the current transaction during afterCompletion as its an "undefined context". Feel free to add me back in if you disagree. Tom
Verified with EAP 6.4.17.CP.CR3
Released on 2017-09-05 as part of the EAP 6.4.17 release.