Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via java.com by Unknown author, 1 year ago
LDAP response read timed out, timeout used:30000ms.
via java.com by Unknown author, 2 years ago
via java.com by Unknown author, 2 years ago
via Oracle Community by 920301, 1 year ago
LDAP response read timed out, timeout used:2000ms.
via atlassian.com by Unknown author, 2 years ago
via atlassian.com by Unknown author, 2 years ago
javax.naming.NamingException: LDAP response read timed out, timeout used:30000ms.	at com.sun.jndi.ldap.Connection.readReply(Connection.java:448)	at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)	at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:192)	at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2694)	at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293)	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 javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)	at javax.naming.InitialContext.init(InitialContext.java:223)	at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)	at LdapReadTimeout.connect(LdapReadTimeout.java:35)	at LdapReadTimeout.doTest(LdapReadTimeout.java:83)	at LdapReadTimeout.main(LdapReadTimeout.java:141)