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 Jaeki Hong, 1 year ago
Failed to connect to node-118/172.23.118.1:57186
via amazon.com by Unknown author, 2 years ago
Failed to connect to ip-172-31-44-240.eu-west-1.compute.internal/172.31.44.240:51083
via amazon.com by Unknown author, 2 years ago
Failed to connect to ip-172-31-44-240.eu-west-1.compute.internal/172.31.44.240:51083
via Stack Overflow by inteloid
, 2 years ago
Failed to connect to cluster3/192.168.10.3:43492
java.net.ConnectException: Connection refused: node-118/
 172.23.118.1:57186	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:208)	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:287)	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)	at java.lang.Thread.run(Thread.java:745)