Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. EventQueue.dispatchEventImpl() has thrown a CannotConnectException
    Java Runtime
    0
    2
    0
  2. Java Runtime cannot connect a dual (IPV4/IPV6) network socket
    Java Runtime
    170
    120
    49

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
java.net.ConnectException: Connection timed out: connect
6 matching frames hidden
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at org.jboss.remoting.transport.socket.SocketClientInvoker.connect(SocketClientInvoker.java:293)
    at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:210)
30 frames hidden

External results for this pattern (10)

  1. xenoterracidevia GitHub1 day ago
    Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    Show stack trace
  2. tbernevia GitHub1 day ago
    org.hibernate.exception.JDBCConnectionException: Cannot open connection
    Show stack trace
  3. sheiktajudeenvia GitHub2 days ago
    java.net.ConnectException: Connection refused: connect
    Show stack trace
  4. ApfelWurmervia GitHub4 days ago
    Error setting up client lease upon performing connect.
    Show stack trace
  5. dbegineervia GitHub6 days ago
    Connect to localhost:8468 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
    Show stack trace
  6. JackTreblevia GitHub1 week ago
    Connection refused: connect
    Show stack trace
  7. ElderJamesvia GitHub1 week ago
    Connection refused: connect
    Show stack trace
  8. InUrSysvia GitHub3 weeks ago
    Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    Show stack trace
  9. InUrSysvia GitHub3 weeks ago
    Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    Show stack trace