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 Atlassian JIRA by Gurleen Anand [Atlassian], 1 year ago
java.net.ConnectException: Connection refused: no further information
via Atlassian JIRA by Gurleen Anand, 1 year ago
java.net.ConnectException: Connection refused: no further information
via Google Groups by Thibault Meyer, 1 year ago
java.lang.RuntimeException: No CSRF token present!
via GitHub by boughtonp
, 1 month ago
com.lambdaworks.io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.5.245:6379
via JIRA by Maxim Kondratenko, 11 months ago
java.lang.IllegalStateException: Connection point not associated with an infrastructure device
via Stack Overflow by Ana Franco
, 1 year ago
java.net.ConnectException: General SSLEngine problem
java.net.ConnectException: Connection refused: no further information	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)	at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:173)	at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:147)	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:350)	at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:191)	at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)	at java.lang.Thread.run(Thread.java:745)