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

Samebug tips

  1. ,
    Expert tip

    This was a bug at HBase 1.0.1, it has been patched, so an update to 1.0.2 or further should solve the problem. URL for the Jira thread: https://goo.gl/c5oa6f

Solutions on the web

via Mojang JIRA by Mike Jones, 1 year ago
Connection timed out: no further information: /**.***.***.**:*****
via Mojang JIRA by Mike Jones, 1 year ago
Connection timed out: no further information: /**.***.***.**:*****
via GitHub by SinzPet
, 2 years ago
Connection timed out: no further information: /192.168.0.108:59502
via GitHub by railstar0083
, 2 years ago
Connection refused: no further information: /108.170.33.141:25565
via planetminecraft.com by Unknown author, 1 year ago
Connection refused: no further information: /10.1.1.99:25565
via Google Groups by Seb Heymann, 2 years ago
Connection refused: no further information: localhost /127.0.0.1:80
java.net.ConnectException: Connection timed out: no further information: /**.***.***.**:*****	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:191)	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:228)	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:497)	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:447)	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:341)	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)	at java.lang.Thread.run(Unknown Source)