Closed Bug 176760 Opened 22 years ago Closed 21 years ago

LDAP client not unbinding - causing LDAP server to hang

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 206018

People

(Reporter: terry_kiliwnik, Assigned: sspitzer)

References

Details

When using the Address Book window the LDAP client in Netscape 7.0 and Mozilla 1.2b (20021016) does not unbind when making search requests to an LDAP server. This is causing our LDAP server to hang after the 64 file descriptors are consumed. Log of LDAP server is below: Oct 22 13:54:30 naos slapd[224]: conn=24 fd=5 connection from net10.nurse.umanitoba.ca (130.179.148.110) accepted. Oct 22 13:54:30 naos slapd[224]: conn=24 op=0 BIND dn="" method=128 Oct 22 13:54:30 naos slapd[224]: conn=24 op=0 RESULT err=0 tag=97 nentries=0 Oct 22 13:54:30 naos slapd[224]: conn=24 op=1 SRCH base="o=university of manitoba,c=ca" scope=2 filter="(|(mail=*GEHLEN*)(cn=*GEHLEN*)(givenname=*GEHLEN*)(sn=*GEHLEN*))" Oct 22 13:54:31 naos slapd[224]: conn=24 op=1 RESULT err=0 tag=101 nentries=1 Here's an example of correct client behavior... Oct 22 13:54:43 naos slapd[224]: conn=25 fd=14 connection from net11.fins.umanitoba.ca (130.179.249.51) accepted. Oct 22 13:54:43 naos slapd[224]: conn=25 op=0 BIND dn="" method=128 Oct 22 13:54:43 naos slapd[224]: conn=25 op=0 RESULT err=0 tag=97 nentries=0 Oct 22 13:54:43 naos slapd[224]: conn=25 op=1 SRCH base="o=University of Manitoba,c=ca" scope=2 filter="(sn=*BUTLER*)" Oct 22 13:54:43 naos slapd[224]: conn=25 op=1 RESULT err=0 tag=101 nentries=6 Oct 22 13:54:43 naos slapd[224]: conn=25 op=2 UNBIND Oct 22 13:54:43 naos slapd[224]: conn=25 op=2 fd=14 closed errno=0
I am not sure what the policy is in the Address Book or Mozilla client LDAP common code, but this is probably not an LDAP C SDK issue. Reassigning.
Assignee: mcs → racham
Component: LDAP Tools → Address Book
Product: Directory → MailNews
QA Contact: nobody → nbaca
Also, I assume that 64 connections are used up by 64 different clients? Or does the Mozilla client repeatedly open new LDAP connections without closing the old ones?
The Mozilla client repeatedly opens a new connection without closing the old ones. A single client would hang the LDAP server after doing 64 searches. All connections are finally closed when Netscape is terminated.
QA Contact: nbaca → gchan
I think Cavin can help out on this one.
Assignee: racham → cavin
taking, working on bug #206018, which is related (or a dup, but let's leave both open.) from http://bugzilla.mozilla.org/show_bug.cgi?id=206018#c5: "while the alert is unique to LDAP over SSL, we have the same problem with non-SSL LDAP connections. on shutdown, they aren't closed cleanly either. (I'm sure the LDAP server logs are showing this, and this isn't nice of us.)"
Assignee: cavin → sspitzer
Depends on: 206018
Each attempt by the address book to query the LDAP server opens an additional connection which stays in "ESTABLISHED" until the entire client is closed with all instances of Mozilla having exited. At that time the connects close. This is consistantly reproduceable with Mozilla 1.3, 1.4, and 1.5 I have been in contact with the submitter of the bug. Their solution has involved an infrastructure change to accomodate this issue. We are evaluating making Mozilla a supported option in our organization. We have already doubled the number of available connections to deal with current usage of Mozilla, but this workaround will not scale if there is widespread adoption of Mozilla. Until this bug is resolved it does not look like we will be able to move forward with rolling it out. I am unable to change the Severity of this ticket - so I'll just state here that this is Blocking our use of Mozilla. I would appreciate an update on the status of this bug as we are evaluating our options for how to proceed. Thanks!
*** Bug 185809 has been marked as a duplicate of this bug. ***
*** Bug 224280 has been marked as a duplicate of this bug. ***
This is also a major block to Mozilla rollout to our 10,000 seats. Is there a workaround?
If any developer needs access to an LDAP/SSL directory for testing, see this comment: http://bugzilla.mozilla.org/show_bug.cgi?id=206018#c9
this is fixed in the latest Seamonkey 1.7 builds and thunderbird - this is a dup.
*** This bug has been marked as a duplicate of 206018 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
No longer depends on: 206018
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.