Bug 1378396

Summary:	[GSS](6.4.z) Transaction context should not be propagated when calling remote server asynchronously
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tom Ross <tom.ross>
Component:	EJB	Assignee:	Flavia Rainone <frainone>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.9	CC:	bmaxwell, david.lloyd, fgavrilo, jbilek, msochure, ochaloup, sappleto
Target Milestone:	CR1
Target Release:	EAP 6.4.13
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1378454 (view as bug list)		Environment:
Last Closed:	2017-02-03 16:43:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1378454, 1386335

Description Tom Ross 2016-09-22 10:38:36 UTC

When an EJB call is made asynchronously between two JBoss servers the transaction context should not be propagated as per EJB spec.

EJB 3.2 4.5.3 Transactions
The client’s transaction context does not propagate with an asynchronous method invocation. From the
Bean Provider’s point of view, there is never a transaction context flowing in from the client. This
means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous
method are exactly the same as REQUIRES_NEW.

Comment 3 Jiří Bílek 2017-01-02 09:14:51 UTC

Verified with EAP 6.4.13.CP.CR1

Comment 4 Petr Penicka 2017-02-03 16:43:58 UTC

Released with EAP 6.4.13 on Feb 02 2017.