Bug 778556 (SOA-1028) - Fix JmsRouter's use of JMS session/providers
Summary: Fix JmsRouter's use of JMS session/providers
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1028
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-14 17:54 UTC by Kevin Conner
Modified: 2014-05-27 01:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-17 08:14:57 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778555 0 high CLOSED Fix JmsRouter's use of JMS session/providers 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1028 0 None None None Never

Internal Links: 778555

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
Note You need to log in before you can comment on or make changes to this bug.