Re: Deadlock occurred between two threads when using Netscape LDAP classes

On Mon, Mar 14, 2011 at 9:30 AM, Zvieli, Asaf <[email protected]> wrote:
> Hi,
>
> I am running my application on JBoss and using ldapjdk.jar to authenticat=
e with LDAP server.
> After a while I am getting a deadlock and my application is crush due to =
out of memory exception.
> In the thread dump I took I see the following error which repeat 660 time=
s:
> Found one Java-level deadlock:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> "LDAPConnThread honts0006:3268":
> =A0waiting to lock monitor 0x680da90c (object 0x27f82bf8, a netscape.ldap=
.LDAPConnection),
> =A0which is held by "http-0.0.0.0-8080-64"
> "http-0.0.0.0-8080-64":
> =A0waiting to lock monitor 0x680da4cc (object 0x27f80368, a netscape.ldap=
.LDAPConnThread),
> =A0which is held by "LDAPConnThread honts0006:3268"
>
> Java stack information for the threads listed above:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> "LDAPConnThread honts0006:3268":
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnection.deregisterConnection(U=
nknown Source)
> =A0 =A0 =A0 =A0 =A0- waiting to lock <0x27f82bf8> (a netscape.ldap.LDAPCo=
nnection)
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnThread.cleanUp(Unknown Source)
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnThread.networkError(Unknown S=
ource)
> =A0 =A0 =A0 =A0 =A0- locked <0x27f80368> (a netscape.ldap.LDAPConnThread)
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnThread.run(Unknown Source)
> "http-0.0.0.0-8080-64":
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnThread.getClientCount(Unknown=
 Source)
> =A0 =A0 =A0 =A0 =A0- waiting to lock <0x27f80368> (a netscape.ldap.LDAPCo=
nnThread)
> =A0 =A0 =A0 =A0 =A0at netscape.ldap.LDAPConnection.disconnect(Unknown Sou=
rce)
> =A0 =A0 =A0 =A0 =A0- locked <0x27f82bf8> (a netscape.ldap.LDAPConnection)
> =A0 =A0 =A0 =A0 =A0at com.mercury.td.ldap.CLdapCommandFactory$CLdapMacroC=
ommand.execute(CLdapCommandFactory.java:1036)
> =A0 =A0 =A0 =A0 =A0- locked <0x27f83a20> (a com.mercury.td.ldap.CLdapComm=
andFactory$CLdapMacroCommand)
> =A0 =A0 =A0 =A0 =A0at com.mercury.td.saserver.api.logics.CTdUserLogic.imp=
ortUserFromLdap(CTdUserLogic.java:1786)
> =A0 =A0 =A0 =A0 =A0at com.mercury.td.saserver.api.logics.CTdUserLogic.imp=
ortUserFromLdap(CTdUserLogic.java:1476)
>
> I did look for this case in the net and found that ORACLE did report on s=
uch a bug in their WebLogic resolve problems but without specific details(s=
ee: http://download.oracle.com/docs/cd/E13222_01/wls/docs61/notes/bugfixes2=
.html , security section, CR125520).
>
>
> 1. =A0 =A0Is this a known issue?
>
> 2. =A0 =A0If it is a known issue, Where can I see the documentation about=
 it?
>
> 3. =A0 =A0 =A0 If it is a known issue and you already fixed it, in which =
ldapjdk.jar version should I use to have the fix in it?

I don't see this issue here -
https://bugzilla.mozilla.org/buglist.cgi?product=3DDirectory&component=3DLD=
AP%20Java%20SDK&resolution=3D---

Please file a bug.

>
> Asaf Zvieli
> HP Software, Quality Center RnD.
> 972.3.5397017 office | 972.3.5331617 fax | [email protected]<mailto:amit=
[email protected]>
> 19 Shabazi Street | 56100 | Yahud | Israel
>
> _______________________________________________
> dev-tech-ldap mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-ldap
>