-
Bug
-
Resolution: Done
-
Major
-
8.1.0.Final
-
None
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.
- causes
-
JBEAP-13681 [GSS](7.2.0) Default SFSB Lifecycle methods transaction attribute causing warnings
- Closed
-
JBEAP-13682 [GSS](7.1.z) Default SFSB Lifecycle methods transaction attribute causing warnings
- Closed
-
WFLY-9509 Default SFSB Lifecycle methods transaction attribute causing warnings
- Closed
-
JBEAP-13689 [GSS](7.0.z) Default SFSB Lifecycle methods transaction attribute causing warnings
- Closed
- is cloned by
-
JBEAP-11846 Wrong Transaction behaviour for EJBs if JTS is enabled
- Closed
- relates to
-
WFLY-4002 avoid arjuna "detected that the transaction was inactive" warnings from org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion
- Closed