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 DouglasJohnson, 1 year ago
failed to connect to 169.254.182.77:9111:228.9.0.164:18979:Cluster2:Cluster2-Node1-Instance
via java.net by Unknown author, 2 years ago
failed to connect to 10.133.184.137:9090:230.30.1.1:9090:clusterz1:Unknown_10.133.184.137_9090
java.net.ConnectException: Connection timed out	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)	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.grizzly1_9.GrizzlyTCPConnectorWrapper$CloseControlCallbackHandler.onConnect(GrizzlyTCPConnectorWrapper.java:185)	at com.sun.grizzly.CallbackHandlerContextTask.doCall(CallbackHandlerContextTask.java:70)