Bug 779663 (SOA-2029)
| Summary: | JmsConnectionPool performs JNDI lookup for connection factory every time it obtains a session | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Kevin Conner <kevin.conner> |
| Component: | JBossESB | Assignee: | 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-2029 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-05-31 09:07:40 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: | |
| Embargoed: | |||
|
Description
Kevin Conner
2010-04-06 12:59:35 UTC
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: 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. |