cancel
Showing results for 
Search instead for 
Did you mean: 

Multithreaded application hangs accessing LDAP

Former Member
0 Kudos

Hi!

Since recently we have noticed our portal hangs without any obvious reason. We have taken thread dumps and it shows error lines as similar to the below. Only work around for this restarting the server. Deep analysis of the thread shows that the Having analysed the issue and discussed it with colleagues, we believe that threads become blocked as the j2ee server tries to connect to the ldap server unsuccessfully.

at java.lang.Object.wait(Native Method)

- waiting on <800003ff6ba534a0> (a com.sun.jndi.ldap.LdapRequest)

at com.sun.jndi.ldap.Connection.readReply(Connection.java:418)

- locked <800003ff6ba534a0> (a com.sun.jndi.ldap.LdapRequest)

at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)

- locked <800003ff6ba53500> (a com.sun.jndi.ldap.LdapClient)

at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:193)

- locked <800003ff6ba53500> (a com.sun.jndi.ldap.LdapClient)

at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)

at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290)

at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)

at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)

at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)

at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:65)

Can anyone advice us why we are getting this and how we can overcome this issue?

Regards

Ramesh

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Ramesh,

We encountered a similar issue today with one of our portal instances. Were you able to figure out what causes this issue?

Regards,

Melwyn

Former Member
0 Kudos

Is the LDAP being used giving any indications of behaving slowly? The LDAP is normally only read at logon time and if something is causing a lot of requests it could happen...