Bug 1018857

Summary:	Note about not direct support nested transaction
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Ondrej Chaloupka <ochaloup>
Component:	Documentation	Assignee:	David Michael <dmichael>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Hayk Hovsepyan <hhovsepy>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	dmichael, hhovsepy, twells
Target Milestone:	post-GA	Keywords:	Documentation
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 14875, Development Guide-6.2-1 Build Date: 02-10-2013 13:20:00 Topic ID: 4287-435148 [Latest]
Last Closed:	2014-11-23 23:17:10 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:

Description Ondrej Chaloupka 2013-10-14 14:26:47 UTC

Title: About Nested Transactions

Please add to the paragraph about nested transaction that setting transaction to use JTS does not mean that the EAP would use the nested transaction. As JTA - API which is used to communicate with TM - does not support nested transactions the EAP does not offer it directly. When user wants to use the nested transaction he needs to touch directly the Narayana ORB api.

Comment 2 Ondrej Chaloupka 2014-07-22 12:18:04 UTC

It does not seem that changes was done as it's mentioned in the comment.

I've read the section once more and more or less I agree with content but, please, add a sentence (or paragraph) which will say something like:
'Changing EAP6 configuration of transaction subsystem to use JTS does not mean that nested transaction will be used/activated. If you need to use them you have to directly use ORB api as JTA api does not provide any method to start nested transaction."

Comment 5 Hayk Hovsepyan 2014-09-22 09:07:38 UTC

Verified on Revision 6.3.0-31