javax.naming.CommunicationException: 1.11.1.1:389 [Root exception is java.net.ConnectException: Connection timed out: connect]

Server Fault | Himanshu Yadav | 5 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

    LDAP Connection TimeOut Exception

    Server Fault | 5 years ago | Himanshu Yadav
    javax.naming.CommunicationException: 1.11.1.1:389 [Root exception is java.net.ConnectException: Connection timed out: connect]
  2. 0

    java LDAP read timeout when timeout is not reached?

    Stack Overflow | 2 years ago | Seephor
    javax.naming.CommunicationException: XX.XX.XX.XX:636 [Root exception is java.net.SocketTimeoutException: Read timed out]
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    JNDI & SSL

    Oracle Community | 2 decades ago | 843793
    javax.naming.CommunicationException: 192.168.0.8:636. Root exception is java.lang.IllegalArgumentException: object is not an instance of declaring class
  5. 0

    javax.naming.CommunicationException

    Oracle Community | 1 decade ago | 843793
    javax.naming.CommunicationException: myserver:389 [Root exception is java.net.ConnectException: Connection timed out: connect]

    1 unregistered visitors
    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.CommunicationException

      1.11.1.1:389 [Root exception is java.net.ConnectException: Connection timed out: connect]

      at com.sun.jndi.ldap.Connection.<init>()
    2. Java RT
      Connection.<init>
      1. com.sun.jndi.ldap.Connection.<init>(Connection.java:208)
      1 frame