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 GitHub by sattishv
, 1 year ago
Connection refused: /172.17.0.2:9994
via GitHub by yadid
, 1 year ago
Connection refused: /198.18.102.141:9042
via GitHub by dinesh4747
, 1 year ago
Connection refused: /10.63.68.44:9994
via GitHub by eysdo
, 5 months ago
Connection refused: /192.168.10.102:9994
via GitHub by siggy
, 1 year ago
Connection refused: /10.0.1.66:29574
via bookkeeper-user by Sebastián Schepens, 7 months ago
Connection refused: /10.3.3.41:3181
java.net.ConnectException: Connection refused: /172.17.0.2:9994	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)	at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150)	at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105)	at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79)	at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)	at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)	at java.lang.Thread.run(Thread.java:745)