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

[Tom Jenkinson (JIRA)]

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

Tom Jenkinson edited comment on WFLY-3801 at 10/23/14 9:11 AM:
---------------------------------------------------------------

Hi David,

I think we should tackle the logging questions separate to this Jira and shouldn't hold up merging it on account of them. It will be easiest to discuss the logging questions on the forum.

In a nutshell, getStatus() is being called in an "undefined context" and so Arjuna is logging a warning. In this case it is hibernate calling getStatus, not WFLY and as an aside, if you used a different persistence provider it might not call getStatus here.

Tom


was (Author: tomjenkinson):
Hi David,

I think we should tackle the logging queries separate to this Jira as shouldn't hold up merging this one and we can discuss it further on the forum best I would say.

In a nutshell, getStatus() is being called in an "undefined context" and so Arjuna is logging a warning. In this case it is hibernate calling getStatus, not WFLY and as an aside, if you used a different persistence provider it might not call getStatus here.

Tom

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