getCollectionNames() causing a "ids don't match" exception intermittently

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.9.3
    • Component/s: Error Handling
    • None
    • Environment:
      Mavericks
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I'm running into an intermittent error when running a bunch of unit tests (though it also occurs when I run a specific test). Before running the tests I clear the mongo database table by table. Every now and then I get the following:

      Oct 31, 2013 1:22:27 PM com.mongodb.DBPortPool gotError
      WARNING: emptying DBPortPool to /127.0.0.1:27017 b/c of error
      com.mongodb.MongoException: ids don't match
      at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:285)
      at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:256)
      at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:289)
      at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:274)
      at com.mongodb.DB.getCollectionNames(DB.java:381)
      at com.parc.cip.repository.MongoDatabaseBridge.cleanDB(MongoDatabaseBridge.java:74)

      the line in file is:

      Set<String> collectionNames = db.getCollectionNames();

      This has been replicated on a few different machines. I am running 2.4.7 of the mongo database.

            Assignee:
            Unassigned
            Reporter:
            Simon Tucker [X]
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: