Bug 779663 (SOA-2029) - JmsConnectionPool performs JNDI lookup for connection factory every time it obtains a session
Summary: JmsConnectionPool performs JNDI lookup for connection factory every time it o...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2029
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.2
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-06 12:59 UTC by Kevin Conner
Modified: 2010-06-11 06:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-31 09:07:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2029 0 None None None Never

Description Kevin Conner 2010-04-06 12:59:35 UTC
Date of First Response: 2010-05-31 05:07:40
project_key: SOA

Comment 1 Kevin Conner 2010-04-06 12:59:59 UTC
Link: Added: This issue depends JBESB-3265


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

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

Comment 4 Dana Mison 2010-06-08 03:46:32 UTC
More information need for release notes:

I assume that this is a performance related issue.  Under what circumstances will the JNDI lookup be performed now ?

Comment 5 Kevin Conner 2010-06-08 10:05:39 UTC
Yes, this is performance related.

The code previously performed a JNDI lookup of the connection factory for every session retrieved from the pool.  It should now only do a lookup when the connection factory has to be discovered, which is the first access or when the connection is in error.

Comment 6 Dana Mison 2010-06-11 06:17:30 UTC
Added to the SOA 5.0.2 release notes as resolved:

JBESB-3265 

JmsConnectionPool was performing a JNDI lookup of the connection factory for every session obtained from the connection pool.  This lookup is now only done when the connection factory is first accessed or when the connection returns an error.  This provides faster performance.






Note You need to log in before you can comment on or make changes to this bug.