Bug 779662 (SOA-2028)

Summary: JmsConnectionPool searches for associated JmsSessionPool by sequentially iterating over JmsSessions
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2028
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-31 09:07:05 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 2010-04-06 12:58:09 UTC
Date of First Response: 2010-05-31 05:07:05
project_key: SOA

Comment 1 Kevin Conner 2010-04-06 12:58:42 UTC
Link: Added: This issue depends JBESB-3263


Comment 2 Kevin Conner 2010-04-26 09:03:55 UTC
Updated in ESB, will be in next merge.

Comment 3 Jiri Pechanec 2010-05-31 09:07:05 UTC
Verified in CR1 sources

Comment 4 Dana Mison 2010-06-09 04:27:49 UTC
More info required for SOA 5.0.2 release notes:

This is purely a performance fix ?

JmsConnectionPool now searchs for associated JmsSessionPools by ???

Comment 5 Kevin Conner 2010-06-09 08:39:26 UTC
Yes, this is a performance fix.  The sessions now contain a reference to their associated pool, using this rather than a search of all the pools.

Comment 6 Dana Mison 2010-06-15 07:10:57 UTC
Added to the SOA 5.0.2 release notes as resolved:

JBESB-3263
JmsConnectionPool searched for associated JmsSessionPools by sequentially iterating over all JmsSessions.
JmsSession now contains a reference to its associated pool so this search does not have to be done.  This provides
faster performance.