reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']

Google Groups | Rémy Phelipot | 9 months ago
  1. 0

    Slow connection causes 'Missing metadata error'?

    Google Groups | 9 months ago | Rémy Phelipot
    reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']
  2. 0

    ConnectionNotInitialized exception on MongoDB write operation

    Stack Overflow | 8 months ago | thwiegan
    reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']
  3. 0

    GridFs error ConnectionNotInitialized: MongoError 'Connection is missing metadata (like protocol

    Google Groups | 1 year ago | Isman Usoh
    reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    ConnectionNotInitialized whilst trying to perform bulkInsert (fine for normal inserts)

    Google Groups | 1 year ago | Duncan Watson
    reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']
  6. 0

    from reactivemongo 0.11.6 to 0.11.11 (& play 2.3 to play 2.4)

    Google Groups | 8 months ago | Ugo Bourdon
    reactivemongo.core.errors.ConnectionNotInitialized: MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']

    1 unregistered visitors
    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. reactivemongo.core.errors.ConnectionNotInitialized

      MongoError['Connection is missing metadata (like protocol version, etc.) The connection pool is probably being initialized.']

      at reactivemongo.core.errors.ConnectionNotInitialized$.MissingMetadata()
    2. reactivemongo.core.errors
      ConnectionNotInitialized$.MissingMetadata
      1. reactivemongo.core.errors.ConnectionNotInitialized$.MissingMetadata(errors.scala:67)
      1 frame
    3. reactivemongo.api.collections
      GenericCollection$$anonfun$insert$1.apply
      1. reactivemongo.api.collections.GenericCollection$$anonfun$insert$1.apply(genericcollection.scala:268)
      2. reactivemongo.api.collections.GenericCollection$$anonfun$insert$1.apply(genericcollection.scala:251)
      2 frames
    4. Scala
      ForkJoinWorkerThread.run
      1. scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
      2. scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
      3. scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)
      4. scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
      5. scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
      6. scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
      7. scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
      8. scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
      8 frames