[
https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-3801:
------------------------------------
Is there an updated test case? With current WildFly master, switching to jts and doing a
{quote}java -cp
$WF/bin/client/jboss-client.jar:target/test-classes:target/ejb30-jpa-client.jar
org.jboss.wfink.ejb30.StatelessMain{quote}, gives me a
[
https://gist.github.com/scottmarlow/4b93269c8b66917c8601] error. I'll turn on trace
to get more info.
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)