[jboss-jira] [JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled
[
https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin....
]
Mark Little commented on WFLY-3801:
-----------------------------------
Whilst the warning message may be visible through getStatus, it's not getStatus which
is generating it. In this case in order to find the status we're potentially having to
make some remote calls and one of the methods needed to do that is causing the warning.
Unfortunately the method is used in many other places where missing the warning could
cause serious problems for the application. Masking it in this one specific case would be
problematical, to say the least.
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)