MongoException$Network on stale connection pool for selection queries only

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.7.2
    • Component/s: API
    • None
    • Environment:
      OSX Lion
      Java 1.6
      Mongo 2.0.0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Steps to reproduce

      1. Establish connection to mongo (i.e.: execute a single query)
      2. Pause java process and stop/start mongo process
      3. Perform one or more selection queries in java process (the first selection query ends with the exception below, all remaining queries succeed.)

      This may be the expected behavior in this scenario but was surprising since inserts do not exhibit the behavior.

      Exception:

      com.mongodb.MongoException$Network: can't call something : /127.0.0.1:27017/connection_test
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:227)
      at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:305)
      at com.mongodb.DBCursor._check(DBCursor.java:369)
      at com.mongodb.DBCursor._hasNext(DBCursor.java:498)
      at com.mongodb.DBCursor.hasNext(DBCursor.java:523)
      at foobar.Testing123.readTest(Testing123.java:65)
      at foobar.Testing123.main(Testing123.java:38)
      Caused by: java.io.EOFException
      at org.bson.io.Bits.readFully(Bits.java:37)
      at org.bson.io.Bits.readFully(Bits.java:28)
      at com.mongodb.Response.<init>(Response.java:39)
      at com.mongodb.DBPort.go(DBPort.java:128)
      at com.mongodb.DBPort.call(DBPort.java:79)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:218)
      ... 6 more

            Assignee:
            Jeffrey Yemin
            Reporter:
            Nick Matheson
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: