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 Oracle Community by bland999, 1 year ago
failed to connect to 10.248.0.170:9146:228.9.13.150:4821:testcluster1:tc1in2
via Oracle Community by bland999, 1 year ago
failed to connect to 10.248.0.170:9146:228.9.13.150:4821:testcluster1:tc1in2
via Oracle Community by bland999, 1 year ago
failed to connect to 10.248.0.170:9146:228.9.13.150:4821:testcluster1:tc1in2
java.net.ConnectException: Connection timed out: no further information	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567)	at com.sun.grizzly.TCPConnectorHandler.finishConnect(TCPConnectorHandler.java:297)	at com.sun.grizzly.connectioncache.client.CacheableConnectorHandler.finishConnect(CacheableConnectorHandler.java:230)	at com.sun.enterprise.mgmt.transport.grizzly.GrizzlyTCPConnectorWrapper$CloseControlCallbackHandler.onConnect(GrizzlyTCPConnectorWrapper.java:184)	at com.sun.grizzly.CallbackHandlerContextTask.doCall(CallbackHandlerContextTask.java:70)	at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)	at com.sun.grizzly.ContextTask.run(ContextTask.java:71)	at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)	at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)	at java.lang.Thread.run(Thread.java:662)