javax.naming.NamingException: LDAP response read timed out, timeout used:300000ms.; Remaining name: 'ou=internal,dc=XXXXX,dc=XXXXX,dc=com'

ibm.com | 8 months ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    IBM IV52561: JNDI TIMEOUT FAILS BEFORE TIMEOUT IS REACHED - United States

    ibm.com | 11 months ago
    javax.naming.NamingException: LDAP response read timed out, timeout used:300000ms.; Remaining name: 'ou=internal,dc=XXXXX,dc=XXXXX,dc=com'
  2. 0

    IBM IV52561: JNDI TIMEOUT FAILS BEFORE TIMEOUT IS REACHED - United States

    ibm.com | 8 months ago
    javax.naming.NamingException: LDAP response read timed out, timeout used:300000ms.; Remaining name: 'ou=internal,dc=XXXXX,dc=XXXXX,dc=com'
  3. 0

    Could not connect to LDAP after upgrading to jre8 on jboss 4.2.3 GA

    Stack Overflow | 3 years ago | boneash
    javax.naming.NamingException: LDAP response read timed out, timeout used:5000ms.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    LDAP bulk import - Forums | Liferay

    liferay.com | 1 year ago
    javax.naming.NamingException: LDAP response read timed out, timeout used:15000ms.; remaining name ''
  6. 0

    JNDI naming exception on JRE7

    Stack Overflow | 2 years ago | Show Stopper
    javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.naming.NamingException

      LDAP response read timed out, timeout used:300000ms.; Remaining name: 'ou=internal,dc=XXXXX,dc=XXXXX,dc=com'

      at com.sun.jndi.ldap.Connection.readReply()
    2. Java RT
      Connection.readReply
      1. com.sun.jndi.ldap.Connection.readReply(Connection.java:480)
      1 frame