Bug 779613 (SOA-1983)

Summary: javax.jms.IllegalStateException thrown when invoking proxied service with SyncServiceInvoker
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Boris Belovic <bbelovic>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1983
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-11 06:04:50 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 Boris Belovic 2010-03-08 16:02:38 UTC
project_key: SOA

See linked issue for details.

Comment 1 Boris Belovic 2010-03-08 16:02:56 UTC
Link: Added: This issue is related to JBESB-3201


Comment 2 Anne-Louise Tangring 2010-09-21 20:24:13 UTC
This is a candidate for SOA 5.1.0. Not committed. Given that the related JIRA is on ESB, I'm taking a guess here and adding that component. If that is wrong, please fix. 

Comment 3 Kevin Conner 2010-10-06 12:38:54 UTC
I have changed the ESB issue to a blocker for 5.1, doing the same with this SOA issue.

Comment 5 Dana Mison 2011-01-05 00:14:28 UTC
Writer: Added: dlesage


Comment 6 Boris Belovic 2011-02-09 09:43:16 UTC
Verified with SOA-P 5.1 ER9 build. There is no exception thrown in ER9 when service C is called from service A.

Comment 7 David Le Sage 2011-02-11 05:59:48 UTC
Temporarily reopening to update release note info.

Comment 8 David Le Sage 2011-02-11 06:04:41 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3201

A javax.jms.IllegalStateException was thrown when the SyncServiceInvoker  was used to invoke a proxied service. This was because of poor tracking of XA sessions returned to the pool, leading to conflicts.  To fix this issue, some code changes have been made so that the software now tracks session users, producers and consumers and the caching of XA sessions. As a result, this exception no longer occurs.