javax.naming.ServiceUnavailableException: xxx.xxx.xxx:389; socket closed

Oracle Community | 2840602 | 2 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    javax.naming.ServiceUnavailableException: xxx.xxx.xxx:389; socket closed error

    Oracle Community | 2 years ago | 2840602
    javax.naming.ServiceUnavailableException: xxx.xxx.xxx:389; socket closed

    Root Cause Analysis

    1. javax.naming.ServiceUnavailableException

      xxx.xxx.xxx:389; socket closed

      at com.sun.jndi.ldap.Connection.readReply()
    2. Java RT
      LdapCtxFactory.getLdapCtxInstance
      1. com.sun.jndi.ldap.Connection.readReply(Connection.java:437)
      2. com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:338)
      3. com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:190)
      4. com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2720)
      5. com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
      6. com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
      7. com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
      8. com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
      8 frames