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 Stack Overflow by Andreas Folkesson
, 1 year ago
Failed to connect to address: /xxx.xx.x.xxx:47100
via Stack Overflow by DKhanaf
, 1 month ago
Failed to connect to address [addr=10.20.18.104:47100, err=Failed to read remote node recovery handshake (connection closed).]
via nabble.com by Unknown author, 1 year ago
Failed to connect to node (is node still alive?). Make sure that each GridComputeTask and GridCacheTransaction has a timeout set in order to prevent parties from waiting forever in case of network issues [nodeId=6701f10e-8319-47ac-99b2-3521cfaf91ca, addrs=[HDD019/192.168.70.19:47100, /192.168.200.19:47100, /192.168.100.19:47100, /192.168.210.19:47100, /127.0.0.1:47100]]
java.net.ConnectException: Connection refused	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)	at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:111)	at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2360)	at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2501)