JNDI hanging when trying to BIND

Question

We are currently having problems with our application hanging when it tries to obtain LDAP context. I have attached a thread dump. Once all the threads start hanging the weblogic server cannot do any work and needs to be restarted. Any help would be appreciatted.
I can make it happen by creating a load on the server.
Code snippet:
we call a static method to return us a context instance, context is not shared.
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://"+directoryHost+":"+directoryPort);
env.put(Context.SECURITY_PRINCIPAL, name);
env.put(Context.SECURITY_CREDENTIALS, password);
env.put(Context.REFERRAL,"follow");
DirContext ctx = new InitialDirContext(env);
return ctx;
Thread dump (there are a few threads like this)
"ExecuteThread: '36' for queue: 'default'" daemon prio=5 tid=0x2718c808 nid=0x77
c waiting on monitor [0x2852f000..0x2852fdc0]
at java.lang.Object.wait(Native Method)
- waiting on <55e31f0> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:283)
- locked <55e31f0> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:310)
- locked <55e31d8> (a com.sun.jndi.ldap.LdapClient)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:163)
- locked <55e31d8> (a com.sun.jndi.ldap.LdapClient)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2386)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:74)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
60)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.jav
a:78)
at com.truecontext.wasabi.business.util.LDAPUtil.getContext(LDAPUtil.jav
a:318)
at com.truecontext.wasabi.business.devman.dao.SynchronizationProfileDAOi
Planet.getObjectsByFilter(SynchronizationProfileDAOiPlanet.java:562)
at com.truecontext.wasabi.business.devman.dao.SynchronizationProfileDAOi
Planet.getObjectsByFilter(SynchronizationProfileDAOiPlanet.java:544)
at com.truecontext.wasabi.business.devman.dao.SynchronizationProfileDAOi
Planet.findSynchronizationProfileDataByDeviceAndUser(SynchronizationProfileDAOiP
lanet.java:1319)
at com.truecontext.wasabi.business.devman.ejb.DeviceMgrEJB.findSynchroni
zationProfileDataByDeviceAndUser(DeviceMgrEJB.java:6502)
at com.truecontext.wasabi.business.devman.ejb.DeviceMgrEJB_fo5kg5_EOImpl
.findSynchronizationProfileDataByDeviceAndUser(DeviceMgrEJB_fo5kg5_EOImpl.java:7
010)
at com.truecontext.wasabi.business.devman.ejb.DeviceMgrSyncSessionEJB.fi
ndSynchronizationProfileDataByDeviceAndUser(DeviceMgrSyncSessionEJB.java:880)
at com.truecontext.wasabi.business.devman.ejb.DeviceMgrSyncSessionEJB_th
6b7o_EOImpl.findSynchronizationProfileDataByDeviceAndUser(DeviceMgrSyncSessionEJ
B_th6b7o_EOImpl.java:166)
at com.truecontext.wasabi.business.sync.ejb.SFSyncEngineEJB.beginSync(SF
SyncEngineEJB.java:1008)
at com.truecontext.wasabi.business.sync.ejb.SFSyncEngineEJB.doProcess(SF
SyncEngineEJB.java:867)
at com.truecontext.wasabi.business.sync.ejb.SFSyncEngineEJB.doProcess(SF
SyncEngineEJB.java:782)
at com.truecontext.wasabi.business.sync.ejb.SFSyncEngineEJB_62algz_EOImp
l.doProcess(SFSyncEngineEJB_62algz_EOImpl.java:199)
at com.truecontext.wasabi.presentation.sync.servlet.SFSyncListener.onMes
sage(SFSyncListener.java:352)
at com.truecontext.wasabi.presentation.sync.servlet.SFSyncListener.doPos
t(SFSyncListener.java:284)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1058)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:401)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5445)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:780)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3105)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2588)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Environment:
iplanet directory server 5.1 Service Pack 2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_08-b03) (also tried 1.4.2)
OS Name Microsoft Windows 2000 Server
Version     5.0.2195 Service Pack 4 Build 2195
BEA Weblogic Server 7.0 sp2

Answer 1

We are having the same problem as well and this has been reported else where as well.
We were able to reproduce this problem on the full blown Weblogic application, with a simple program which creates a large number of connection in quick succession - after a certain number of connections ( about 60), the client simply hangs! It turns out that this is a known problem with iPlanet 5.1 with SSL: http://www.openldap.org/lists/openldap-software/200205/msg00567.html
I have also posted this message to the Directory Server forum at Sun, but have not heard anything yet!
http://swforum.sun.com/jive/thread.jspa?threadID=46914&tstart=0
There have been quite a few other cases of this problem ( probably manifesting itself in other forms!)
http://forum.java.sun.com/thread.jsp?forum=51&thread=358357
Let me know if you come up with a solution to your problem