Bug 1136054 – [GSS] (6.4.z) Wrong Transaction behaviour for EJBs if JTS is enabled

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	EJB (Show other bugs)
Sub Component:
Version:	6.3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	CR1
Target Release:	EAP 6.4.17
Assigned To:	Radovan Netuka
QA Contact:	Jiří Bílek
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	eap6417-payload 1508105
	Show dependency tree / graph

Reported:	2014-09-01 10:23 EDT by wfink
Modified:	2017-10-31 16:15 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-09-06 09:37:39 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-3801	Major	Closed	Wrong Transaction behaviour for EJBs if JTS is enabled	2018-04-12 09:13 EDT

Groups: None (edit)

Description wfink 2014-09-01 10:23:27 EDT

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
SFSB remove ERROR

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

Hi,

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.

Tom

Comment 7 Jiří Bílek 2017-08-04 11:06:35 EDT

Verified with EAP 6.4.17.CP.CR3

Comment 8 Petr Penicka 2017-09-06 09:37:39 EDT

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.