java.net.ConnectException: ClientRequestExecutor timed out for destination bcn1-cache-vold-095p1:6666(vp1)

Google Groups | Miguel Ausó | 1 year ago
  1. 0

    Voldemort Connection problems

    Google Groups | 1 year ago | Miguel Ausó
    java.net.ConnectException: ClientRequestExecutor timed out for destination bcn1-cache-vold-095p1:6666(vp1)
  2. 0
    DoS protection blocks your client after a certain amount of requests.
  3. 0
    Your firewall blocks the connection, disable it.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0
    To restart the Selenium Webdriver mock browser in a testcase, first use 'driver.close()' and then reinstantiate the driver.
  6. 0
    You close Selenium Webdriver before the tests finish. Use @BeforeSuite and @AfterSuite.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.ConnectException

      ClientRequestExecutor timed out for destination bcn1-cache-vold-095p1:6666(vp1)

      at voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$1.requestComplete()
    2. voldemort.store.socket
      NonblockingStoreCallbackClientRequest.timeOut
      1. voldemort.store.socket.clientrequest.ClientRequestExecutorFactory$1.requestComplete(ClientRequestExecutorFactory.java:210)
      2. voldemort.store.socket.clientrequest.NonblockingStoreCallbackClientRequest.invokeCallback(NonblockingStoreCallbackClientRequest.java:68)
      3. voldemort.store.socket.clientrequest.NonblockingStoreCallbackClientRequest.timeOut(NonblockingStoreCallbackClientRequest.java:128)
      3 frames