Bug 23363 - JNDI Taglib does not close context when using <jndi:useDirContext> tag
Summary: JNDI Taglib does not close context when using <jndi:useDirContext> tag
Status: RESOLVED LATER
Alias: None
Product: Taglibs
Classification: Unclassified
Component: JNDI Taglib (show other bugs)
Version: 1.0
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
: 23364 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-23 19:33 UTC by Mitch Winkle
Modified: 2009-11-29 19:34 UTC (History)
0 users


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

Note You need to log in before you can comment on or make changes to this bug.
Description Mitch Winkle 2003-09-23 19:33:07 UTC 
This is important for freeing network resources on heavily laden web-app servers
as well as the LDAP servers they point at.

I had to add <% contextName.close(); %> to the end of my jsp page in order to do
a timely close of the connection to an LDAP resource.

In my Java code that uses JNDI and LDAP, I just use contextName.close() in the
finally clause so as not to forget :-)
Comment 1 Mitch Winkle 2003-09-25 16:56:08 UTC 
Additionally, if this is to remain flexible, perhaps for JNDI connection
pooling, then why not just offer a :

<jndi:closeContext id="contextName" /> tag similar to what is used in Taglibs
dbtags with <sql:closeConnection conn="connname"/> ?
Comment 2 Mitch Winkle 2003-09-25 16:58:30 UTC 
*** Bug 23364 has been marked as a duplicate of this bug. ***
Comment 3 Henri Yandell 2009-11-29 19:34:53 UTC 
Resolving as the JNDI taglib has been retired.