[
https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-3801:
------------------------------------
Hibernate does have its own sync registered, but it would be a JPA spec violation for
Hibernate to close the entity manager, that is the wrong place to close it from.
For the JTS case, it definitely sounds like there is more overhead introduced to have the
JPA container layer suspend the transaction (e.g. calling suspend on remote coordinator).
I'm going to reject that WFLY-3802 change as it is not required.
Wrong Transaction behaviour for EJBs if JTS is enabled
------------------------------------------------------
Key: WFLY-3801
URL:
https://issues.jboss.org/browse/WFLY-3801
Project: WildFly
Issue Type: Bug
Components: EJB, Transactions
Affects Versions: 8.1.0.Final
Environment: standalone-full profile with JTS enabled
Reporter: Wolf-Dieter Fink
Assignee: David Lloyd
Attachments: 456a624-withDestroy.log, 8d49872-error.log, enableJTS.cli,
reproducer.zip, server.log
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.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)