Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1049610

Summary:	Need to document remote client with UserTransaction fails on 2nd SFSB invocation
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	sgilda
Component:	Documentation	Assignee:	eap-docs <eap-docs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.2.0	CC:	ochaloup, sfolkwil, smarlow
Target Milestone:	---	Keywords:	Documentation, FutureFeature, Reopened
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:44:26 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 sgilda 2014-01-07 20:42:43 UTC

Description of problem:
During migration, remote client with UserTransaction fails on 2nd SFSB invocation when using extended persistence context.

AS5 allowed a remote client to instantiate a set of stateful session beans (e.g. SFSB1 + SFSB2) and then call the remote stateful session beans in a started user transaction (UT1). In AS5, both stateful beans shared the same extended persistence unit context, but on AS7/WF8, each bean has its own extended persistence unit context. In AS 7, using two instances of the same named extended persistence context in the same JTA transaction causes an (EJBException: JBAS011437: Found extended persistence context in SFSB invocation call stack but that cannot be used because the transaction already has a transactional context associated with it...) error to be thrown.

The user application code must be changed to 

For details and code examples, see:

https://issues.jboss.org/browse/WFLY-2504
https://community.jboss.org/message/845455
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 sgilda 2014-04-09 17:13:25 UTC

Scott Marlow reported this one to me. I need to check to see where this stands. Adding him to this bug.

Comment 2 Scott Marlow 2014-04-09 18:26:36 UTC

This is a community reported issue that has not been resolved.  I'm not yet sure what I want to do about it (in terms of whether to make code changes or to disallow the case as not EE spec compliant).  At this moment, it is best to document the issue as being an open migration issue.

Comment 3 sgilda 2014-05-20 20:21:43 UTC

I'm not sure why this bug is a blocker. Only one person in the community has run into this and the code was not compliant.

I recommend we remove the blocking status of this bug.

Comment 4 sgilda 2014-05-20 20:46:19 UTC

Created an initial topic:
Migrate Remote Client with Multiple Stateful Session Beans in a UserTransaction [31290]

Comment 5 Scott Marlow 2014-05-20 20:49:17 UTC

This is not currently a blocker, as only one community user has reported the issue.

Comment 7 Scott Marlow 2014-05-20 23:51:39 UTC

Sande, best, to start with reading the forum post https://community.jboss.org/message/845455 which goes into more detail than the jira.  I'll help answer your questions still of course. :)

Comment 8 sgilda 2014-05-20 23:55:08 UTC

Thanks Scott. I'll do that. :-)

Comment 9 Ondrej Chaloupka 2014-05-23 08:02:36 UTC

As it was mentioned above it's not a doc blocker. Removing the flag from it.