185809 - ldap connections are not closed after searching entries in ldap directory

Status: RESOLVED DUPLICATE of bug 176760

(MailNews Core :: LDAP Integration, defect)

Description

[Patrick Vachon]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

After having found entries in the to: field of the compose window, ldap 
connections aren't close. I found this using netstat on my windows xp 
workstation.

Reproducible: Always

Steps to Reproduce:
1. use a ldap directory
2. find a name in the to: field of the compose window
3. use netstat to find open connections in windows

Actual Results:  
ldap connections aren't closed, my ldap server quickly had no more ldap 
connections available, even if the server may handle more than 2000 connections

Expected Results:  
ldap connections should have been closed

Mozilla 1.2.1 on Windows XP service pack 1
Dell Inspiron 8200

Comment 1

[José Jeria]

*** Bug 185810 has been marked as a duplicate of this bug. ***

Comment 2

[David Mead]

I have seen this same problem today.  A system administrator called to ask why I
had three open connections to the LDAP server.  Our ldap server has come under
increasing stain recently because of unclosed connections.  I am now wondering
if increased Mozilla use is causing this problem.

I confirmed this same situation occurs in Mozilla 1.3 under both Windows XP and
Redhat 8.2.  

This appears to be easily reproducable, unless it is something unique about our
ldap server.

I am willing to provide any additional information that will help resolve this
issue.

Comment 3

[Rob Janssen]

I have seen this happen, but not yet had a problem.
This is with Mozilla 1.3 and OpenLdap V2 or V3.

Until now I believed that it is some "cached LDAP connection" feature and that
there may be some different connections depending on the context (addressbook,
lookup of To: address).

Comment 4

[Nerijus Krukauskas]

I confirm that this happens with my Mozilla 1.4 on Linux and our LDAP Lotus server.

Comment 5

[Mark Smith [:mcs]]

*** This bug has been marked as a duplicate of 176760 ***