Possible deadlock in WLDAP32.dll

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have a multithreaded application running on win2000 (sp4). This application executes LDAP requests against active directory domain controller, or against exchange server.

Using Windbg we have detected a possible deadlock situation


CritSec WLDAP32!ConnectionListLock+0 at 77971768
LockCount 160
RecursionCount 1
OwningThread ef8
EntryCount 8d3aa
ContentionCount 8d3c0
*** Locked

CritSec WLDAP32!RequestListLock+0 at 7796F030
LockCount 11
RecursionCount 1
OwningThread f2c
EntryCount 15ea
ContentionCount 15ea
*** Locked

Thread EF8 call stack:
00000a88 00000000 00000000 NTDLL!NtWaitForSingleObject+0xb
7796f000 7795468a 7796f030 NTDLL!RtlpWaitForCriticalSection+0x9e
7796f030 00000000 1565cd00 NTDLL!RtlEnterCriticalSection+0x46
0029820b 1565cd98 0bb2c4a0 WLDAP32!FindLdapRequest+0x24
0bb2c4a0 0029820b 00000001 WLDAP32!ldap_result_with_error+0xce
0bb2c628 00000000 00000000 WLDAP32!ldap_search_ext_sW+0x84
0bb2c400 1565d11c 10270658 WLDAP32!LdapGetServiceNameForBind+0x1f7
0bb2c400 00000000 00000486 WLDAP32!LdapBind+0x20f
0bb32840 00000003 7796f001 WLDAP32!LdapChaseReferral+0xd63
11d84400 0bb93ba8 0bb32840 WLDAP32!HandleReferral+0x3d3
11d84420 1565d25c 0bb32840 WLDAP32!HandleReferrals+0xc5
11d84420 002981bf 11d84420 WLDAP32!ldap_result_with_error+0x15f
11d845a8 0df2b161 00000002 WLDAP32!ldap_search_ext_sA+0xcb
11d845a8 0df2b161 00000002 WLDAP32!ldap_search_st+0x42
[…]

Thread f2c Call stack:
0000062c 00000000 00000000 NTDLL!NtWaitForSingleObject+0xb
77971700 7795a395 77971768 NTDLL!RtlpWaitForCriticalSection+0x9e
77971768 0bb79088 0bb29010 NTDLL!RtlEnterCriticalSection+0x46
0bb29010 103a5da8 11ebdea0 WLDAP32!CloseLdapConnection+0x41
00000000 77f89103 103a5e98 WLDAP32!DereferenceLdapRequest2+0x155
11ebdeb8 1806d3c0 7795b4ca WLDAP32!CloseLdapConnection+0x208
103a5f30 00000000 00000000 WLDAP32!ldap_unbind+0x58
[…]


WLDAP32.dll 5.00.2195.6666

will the fix posted on 821471 - Deadlock on Wldap32.dll Causes InetInfo.exe to Stop Responding resolve this problem?

Thanks I.A
 
Are you experiencing any of the four symptoms in the kb article? If you
are, then I'd say that's a possibility. It's a post-SP4 hotfix relating to
wldap32.dll, but as with all hotfixes they are only designed to address the
specific symptoms listed in the article.

David Pharr, (e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Possible deadlock in WLDAP32.dll
| thread-index: AcPgEsEWe5zJWvwwTZ6oH7prkQ2TJg==
| X-Tomcat-NG: microsoft.public.win2000.active_directory
| From: =?Utf-8?B?VGFsIFJvc2Vu?= <[email protected]>
| Subject: Possible deadlock in WLDAP32.dll
| Date: Wed, 21 Jan 2004 03:36:05 -0800
| Lines: 55
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.win2000.active_directory
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.active_directory:63655
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| We have a multithreaded application running on win2000 (sp4). This
application executes LDAP requests against active directory domain
controller, or against exchange server.

Using Windbg we have detected a possible deadlock situation


CritSec WLDAP32!ConnectionListLock+0 at 77971768
LockCount 160
RecursionCount 1
OwningThread ef8
EntryCount 8d3aa
ContentionCount 8d3c0
*** Locked

CritSec WLDAP32!RequestListLock+0 at 7796F030
LockCount 11
RecursionCount 1
OwningThread f2c
EntryCount 15ea
ContentionCount 15ea
*** Locked

Thread EF8 call stack:
00000a88 00000000 00000000 NTDLL!NtWaitForSingleObject+0xb
7796f000 7795468a 7796f030 NTDLL!RtlpWaitForCriticalSection+0x9e
7796f030 00000000 1565cd00 NTDLL!RtlEnterCriticalSection+0x46
0029820b 1565cd98 0bb2c4a0 WLDAP32!FindLdapRequest+0x24
0bb2c4a0 0029820b 00000001 WLDAP32!ldap_result_with_error+0xce
0bb2c628 00000000 00000000 WLDAP32!ldap_search_ext_sW+0x84
0bb2c400 1565d11c 10270658 WLDAP32!LdapGetServiceNameForBind+0x1f7
0bb2c400 00000000 00000486 WLDAP32!LdapBind+0x20f
0bb32840 00000003 7796f001 WLDAP32!LdapChaseReferral+0xd63
11d84400 0bb93ba8 0bb32840 WLDAP32!HandleReferral+0x3d3
11d84420 1565d25c 0bb32840 WLDAP32!HandleReferrals+0xc5
11d84420 002981bf 11d84420 WLDAP32!ldap_result_with_error+0x15f
11d845a8 0df2b161 00000002 WLDAP32!ldap_search_ext_sA+0xcb
11d845a8 0df2b161 00000002 WLDAP32!ldap_search_st+0x42
[…]

Thread f2c Call stack:
0000062c 00000000 00000000 NTDLL!NtWaitForSingleObject+0xb
77971700 7795a395 77971768 NTDLL!RtlpWaitForCriticalSection+0x9e
77971768 0bb79088 0bb29010 NTDLL!RtlEnterCriticalSection+0x46
0bb29010 103a5da8 11ebdea0 WLDAP32!CloseLdapConnection+0x41
00000000 77f89103 103a5e98 WLDAP32!DereferenceLdapRequest2+0x155
11ebdeb8 1806d3c0 7795b4ca WLDAP32!CloseLdapConnection+0x208
103a5f30 00000000 00000000 WLDAP32!ldap_unbind+0x58
[…]


WLDAP32.dll 5.00.2195.6666

will the fix posted on 821471 - Deadlock on Wldap32.dll Causes InetInfo.exe
to Stop Responding resolve this problem?

Thanks I.A

|
 
Back
Top