If you like a tip written by other Samebug users, mark is as helpful! Marks help our algorithm provide you better solutions and also help other users.

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:

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • GitHub comment 7489#230246754
    via GitHub by DFoxinator
  • GitHub comment 22#129971600
    via GitHub by zutherb
  • play framework test connection refused
    via Stack Overflow by egcram
  • GitHub comment 292#210218179
    via GitHub by siggy
  • connection refused error
    via GitHub by ebereketoglu
  • Java websocket can't connect
    via by jude chen,
    • MasterClient214 could not connect from /SLAVE1IP:0 to /MASTERIP:6001 at$2.create( at$2.create( at at at at org.neo4j.kernel.ha.MasterClient210.pullUpdates( at org.neo4j.kernel.ha.MasterClient210.pullUpdates( at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at org.neo4j.kernel.ha.DelegateInvocationHandler.proxyInvoke( at org.neo4j.kernel.ha.DelegateInvocationHandler.invoke( at com.sun.proxy.$Proxy3.pullUpdates(Unknown Source) at org.neo4j.kernel.ha.SlaveUpdatePuller.doPullUpdates( at org.neo4j.kernel.ha.SlaveUpdatePuller.periodicallyPullUpdates( at at java.util.concurrent.Executors$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at at org.neo4j.helpers.NamedThreadFactory$ Caused by: Connection refused: /MASTERIP:6001 at Method) at at at at at at at at org.jboss.netty.util.internal.DeadLockProofWorker$ ... 4 more

    Users with the same issue

    8 times, last one,
    Roman LeventovRoman Leventov
    1 times, last one,
    Unknown visitor
    Unknown visitor2 times, last one,
    3 times, last one,
    1 times, last one,
    115 more bugmates