Red Hat Bugzilla – Bug 779663
JmsConnectionPool performs JNDI lookup for connection factory every time it obtains a session
Last modified: 2010-06-11 02:17:54 EDT
Date of First Response: 2010-05-31 05:07:40
Link: Added: This issue depends JBESB-3265
Updated in ESB, will be in next merge.
Verified in CR1 sources
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 ?
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.
Added to the SOA 5.0.2 release notes as resolved:
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.