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 Google Groups by Pankaj Kumar, 1 year ago
Connection timed out: no further information: <server>/<server_ip>:443
via GitHub by zhangshihai1232
, 1 year ago
Connection timed out: no further information: images-na.ssl-images-amazon.com/54.230.145.60:443
via Google Groups by Gadi Eichhorn, 4 months ago
via Google Groups by Thomas Gilbert, 5 months ago
via Google Groups by Rodolfo de Paula, 4 months ago
via YouTrack by Unknown author, 2 years ago
Connection refused: no further information: /127.0.0.1:62009
java.net.ConnectException: Connection timed 
out: no
 further information: <server>/<server_ip>:443	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:329)	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:588)	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:512)	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:426)	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:398)	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:877)	at java.lang.Thread.run(Unknown Source)