Bug 1136054 - [GSS] (6.4.z) Wrong Transaction behaviour for EJBs if JTS is enabled
Summary: [GSS] (6.4.z) Wrong Transaction behaviour for EJBs if JTS is enabled
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: CR1
: EAP 6.4.17
Assignee: Radovan Netuka
QA Contact: Jiří Bílek
Russell Dickenson
Depends On:
Blocks: eap6417-payload 1508105
TreeView+ depends on / blocked
Reported: 2014-09-01 14:23 UTC by wfink
Modified: 2020-05-14 14:55 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-09-06 13:37:39 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3801 0 Major Closed Wrong Transaction behaviour for EJBs if JTS is enabled 2019-02-18 15:18:09 UTC

Description wfink 2014-09-01 14:23:27 UTC
Description of problem:

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.

How reproducible:
With transactional EJB's which are using other Tx resources.

Worse case if a SFSB with a @Remote method is used

Steps to Reproduce:
See WFLY-3801

Actual results:
arjuna WARN messages

Comment 2 tom.jenkinson 2014-09-02 11:22:07 UTC

I removed "Transaction Manager" from this as I don't believe its a TM issue. As discussed on the thread I think EJB should not be trying to access the current transaction during afterCompletion as its an "undefined context".

Feel free to add me back in if you disagree.


Comment 7 Jiří Bílek 2017-08-04 15:06:35 UTC
Verified with EAP 6.4.17.CP.CR3

Comment 8 Petr Penicka 2017-09-06 13:37:39 UTC
Released on 2017-09-05 as part of the EAP 6.4.17 release.

Note You need to log in before you can comment on or make changes to this bug.