Bug 778556 (SOA-1028)

Summary:	Fix JmsRouter's use of JMS session/providers
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Kevin Conner <kevin.conner>
Component:	JBossESB	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CP01
Target Milestone:	---
Target Release:	4.2 CP03
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1028
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-17 08:14:57 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:

Description Kevin Conner 2008-11-14 17:54:05 UTC

Date of First Response: 2008-12-04 20:06:01
project_key: SOA

Platform issue for JBESB-2190

Comment 1 Kevin Conner 2008-11-14 17:54:05 UTC

Link: Added: This issue depends JBESB-2190

Comment 2 Kevin Conner 2008-11-14 17:55:03 UTC

Link: Added: This issue is related to SOA-1027

Comment 3 Dana Mison 2008-12-05 01:06:01 UTC

Regards release notes:

Can I have a clarification on how JMSRouter handles this now?

Comment 4 Kevin Conner 2008-12-05 11:18:33 UTC

Hiya Darrin.

The JmsRouter had been obtaining a single JMS session/provider and sharing this across all invocations of the router.  Such concurrent access is invalid as the JMS session/producer are not thread safe objects.

The JmsRouter now obtains a session/producer from the connection pool and uses it within the scope of a single request before returning it to the pool.

Comment 5 Dana Mison 2008-12-09 03:02:08 UTC

Release Note:
JmsRouter now obtains a different session/producer from the connection pool to be used within the scope of each request rather than sharing one across all invocations of the router.

Comment 6 Jiri Pechanec 2008-12-17 08:14:57 UTC

Verified in CR5 sources