[jboss-jira] [JBoss JIRA] (WFLY-3801) Wrong Transaction behaviour for EJBs if JTS is enabled

[Wolf-Dieter Fink (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013919#comment-13013919 ] 

Wolf-Dieter Fink commented on WFLY-3801:
----------------------------------------

After a look to the current WF upstream I saw a changed behavior.
The server need to be complete restarted (the :reload via CLI did not help after switch JTA->JTS)
but after that the failure is gone and the PREDESTROY method is invoked and the bean seems correct destroyed.

There are only WARN messages left in this case which should be not shown:
17:02:43,694 FATAL [org.jboss.wfink.ejb30.SFTestBean] (EJB default - 1) CONSTRUCT
17:02:43,973 INFO  [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022200: TopLevelTransactionRecoveryModule Second Pass
17:02:43,974 INFO  [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022214: TransactionRecoveryModule.periodicWorkSecondPass()
17:02:43,974 INFO  [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022191: ServerTransactionRecoveryModule - Second Pass
17:03:04,174 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
17:03:04,176 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022015: Interposition.removeHeirarchy - could not find 0:ffffc0a81b32:5e5cee49:54467589:15 to remove.
17:03:26,846 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
17:03:26,849 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022015: Interposition.removeHeirarchy - could not find 0:ffffc0a81b32:5e5cee49:54467589:24 to remove.
Wait 1sec
17:03:32,082 FATAL [org.jboss.wfink.ejb30.SFTestBean] (EJB default - 4) REMOVE
17:03:50,559 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
17:03:50,562 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022015: Interposition.removeHeirarchy - could not find 0:ffffc0a81b32:5e5cee49:54467589:31 to remove.
17:03:54,024 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
17:03:54,030 WARN  [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022015: Interposition.removeHeirarchy - could not find 0:ffffc0a81b32:5e5cee49:54467589:31 to remove.
17:03:54,031 FATAL [org.jboss.wfink.ejb30.SFTestBean] (RequestProcessor-5) DESTROY



The full logfiles with arjuna/jpa TRACE are attached.
8d49872-error.log contains the version where the REMOVE invocation failed
456a624-withDestroy.log contains the version where REMOVE and DESTROY are correct invoked.

The first commit where the behavior has changed is :
commit 456a624d98eaa5f5fc016ad7520290177e3771f6
Author: Stuart Douglas <stuart.w.douglas at gmail.com>
Date:   Fri Oct 3 15:22:20 2014 +1000

    WFLY-3801 Make sure NOT_SUPPORTED and REQUIRES_NEW are the only allowed SFSB lifecycle interceptor transaction attributes


> 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: 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)