[
http://jira.jboss.com/jira/browse/JBAS-3650?page=all ]
Prabhat Jha resolved JBAS-3650.
-------------------------------
Assignee: JBN Patch Team (was: Prabhat Jha)
It did not cause any regression. Here is the md5sum:
e1d378f52c7e7e1caf38ea88ff117406 jbosssx.jar
LdapExtLoginModule still has connection leak
--------------------------------------------
Key: JBAS-3650
URL:
http://jira.jboss.com/jira/browse/JBAS-3650
Project: JBoss Application Server
Issue Type: Support Patch
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-4.0.3 SP1
Reporter: Scott M Stark
Assigned To: JBN Patch Team
Attachments: jbosssx.jar
The fix to close all ldap contexts in JBAS-3448 still was leaving naming enumeration
results open, which is delaying the close of connections to the next gc. We need to
cleanup the ldap search result enumerations as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira