io.searchbox.client.config.exception.NoServerConfiguredException

No Server is assigned to client to connect

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5

  • via GitHub by Kunal-Dethe
    ,
  • Stack trace

    • io.searchbox.client.config.exception.NoServerConfiguredException: No Server is assigned to client to connect at io.searchbox.client.AbstractJestClient$ServerPool.getNextServer(AbstractJestClient.java:132)[jest-common-2.0.2.jar:na] at io.searchbox.client.AbstractJestClient.getNextServer(AbstractJestClient.java:81)[jest-common-2.0.2.jar:na] at io.searchbox.client.http.JestHttpClient.prepareRequest(JestHttpClient.java:80)[jest-2.0.2.jar:na] at io.searchbox.client.http.JestHttpClient.execute(JestHttpClient.java:46)[jest-2.0.2.jar:na] at io.searchbox.client.config.discovery.NodeChecker.runOneIteration(NodeChecker.java:65)[jest-common-2.0.2.jar:na] at com.google.common.util.concurrent.AbstractScheduledService$ServiceDelegate$Task.run(AbstractScheduledService.java:189)[guava-19.0.jar:na] at com.google.common.util.concurrent.Callables$3.run(Callables.java:100)[guava-19.0.jar:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[na:1.8.0_101] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[na:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[na:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[na:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_101] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_101]

    Write tip

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

    Users with the same issue

    We couldn't find other users who have seen this exception.