There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Error in Play-MongoDB.
    via by Tam Truong,
  • Play 2.5 - too many weird errors
    via by Peter,
  • GitHub comment 20#77760351
    via GitHub by pizirun
  • GitHub comment 184#176353782
    via GitHub by wsargent
    • java.util.concurrent.CompletionException: com.mongodb.MongoTimeoutExc eption: Timed out after 30000 ms while waiting for a server that matches ReadPre ferenceServerSelector{readPreference=primary}. Client view of cluster state is { type=UNKNOWN, servers=[{address=locahost:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException: locahost}, caused by { ownHostException: locahost}}] at java.util.concurrent.CompletableFuture.encodeThrowable( at java.util.concurrent.CompletableFuture.completeThrowable( at java.util.concurrent.CompletableFuture.uniApply( at java.util.concurrent.CompletableFuture$UniApply.tryFire( at java.util.concurrent.CompletableFuture.postComplete( at java.util.concurrent.CompletableFuture.completeExceptionally( at scala.concurrent.java8.FuturesConvertersImpl$CF.apply(FutureConvertersImpl.scala:21) at scala.concurrent.java8.FuturesConvertersImpl$CF.apply(FutureConvertersImpl.scala:18) at at scala.concurrent.BatchingExecutor$Batch$$anonfun$run$1.processBatch$1(BatchingExecutor.scala:63)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,