Closed Bug 67413 Opened 24 years ago Closed 24 years ago

Deadlock when disconnecting

Categories

(Directory :: LDAP Java SDK, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Thomas.Beyer, Assigned: miodrag)

References

Details

We sometimes run into a deadlock when trying to disconnect after an attempt to authenticate with invalid credentials: The code sequence is: // ------------------------------------------------------- LDAPConnection conn = new LDAPConnection (); try { conn.connect (host,port); conn.authenticate (invalid_user,invalid_pwd); ... } catch (LDAPException e) { ... } finally { if (conn.isConnected ()) { try { conn.disconnect (); } catch (LDAPException ignored) {} } } // ------------------------------------------------------- And here's the jdb stack trace: LDAPConnThread 127.0.0.1:389: [1] netscape.ldap.LDAPConnection.deregisterConnection (LDAPConnection.java:197) [2] netscape.ldap.LDAPConnThread.cleanUp (LDAPConnThread.java:334) [3] netscape.ldap.LDAPConnThread.networkError (LDAPConnThread.java:627) [4] netscape.ldap.LDAPConnThread.run (LDAPConnThread.java:436) Thread-1: [1] netscape.ldap.LDAPConnThread.getClientCount (LDAPConnThread.java:231) [2] netscape.ldap.LDAPConnection.disconnect (LDAPConnection.java:1896) [3] LdapTest.disconnect (LdapTest.java:368) [4] LdapTest.run (LdapTest.java:293)
How often is "sometimes?" Reassigned to Miodrag so he can take a look.
Assignee: mcs → miodrag
Was not able to reproduce the bug but the stack trace cleary shows where the problem is. The bug has been fixed. Please cvs update and rebuild ldapjdk to pick up the fix.
Status: NEW → RESOLVED
Closed: 24 years ago
Priority: -- → P3
Resolution: --- → FIXED
*** Bug 218742 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.