IZ60793: THREAD HANGS BINDING TO LDAP SERVER
Closed as program error.
Error Message: N/A . Stack Trace: at java/lang/Object.wait(Native Method) at java/lang/Object.wait(Object.java:231(Compiled Code)) at com/sun/jndi/ldap/Connection.readReply(Connection.java:434(Compi led Code)) at com/sun/jndi/ldap/LdapClient.ldapBind(LdapClient.java:355(Compil ed Code)) at com/sun/jndi/ldap/LdapClient.authenticate(LdapClient.java:207(Co mpiled Code)) at com/sun/jndi/ldap/LdapCtx.connect(LdapCtx.java:2652(Compiled Code)) at com/sun/jndi/ldap/LdapCtx.<init>(LdapCtx.java:298(Compiled Code)) . We lost accessibility to both of our production websphere portal instances today. The processes were still running on each host machine but when attempting to access it via its host port, the browser would hang. SystemOut.log shows hung WebContainer threads. Most of these threads are waiting for a response while trying to BIND to the remote LDAP (during WebSphere Portal user login):
Restart LDAP Client
If a client does not receive a response from the LDAP Server when attempting to bind to it, the client will hang.
This defect will be fixed in: 5.0.0 SR11 . A system property com.sun.jndi.ldap.read.timeout has been added to the JVM. If present, the LDAP bind attempt will timeout after the given number of milliseconds have elapsed and the client will throw a NamingException "LDAP response read timed out" . To obtain the fix: Install build 20090926 or later
Reported component name
JAVA 5 CLASS LI
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
JAVA 5 CLASS LI
Fixed component ID
Applicable component levels