Skip to content

Database issue wit MongoDB v2.4.2 #69

@peshkira

Description

@peshkira

There might be a database issue with newer versions of the MongoDB (e.g. 2.4.2).
It seems that there was a read that took too long and caused the connection to be dropped during profile generation. It might be a problem with the java driver and newer Mongo versions, or it might have been the users machine.

Exception in thread "main" com.mongodb.MongoException$CursorNotFound: cursor 0 not found on server localhost/127.0.0.1:27017
        at com.mongodb.DBApiLayer$Result.init(DBApiLayer.java:396)
        at com.mongodb.DBApiLayer$Result._advance(DBApiLayer.java:459)
        at com.mongodb.DBApiLayer$Result.hasNext(DBApiLayer.java:423)
        at com.mongodb.DBCursor._hasNext(DBCursor.java:497)
        at com.mongodb.DBCursor.hasNext(DBCursor.java:517)
        at com.petpet.c3po.dao.mongo.MongoIterator.hasNext(MongoIterator.java:75)
        at com.petpet.c3po.analysis.ProfileGenerator.generateProperties(ProfileGenerator.java:247)
        at com.petpet.c3po.analysis.ProfileGenerator.generateProfile(ProfileGenerator.java:189)
        at com.petpet.c3po.controller.Controller.profile(Controller.java:239)
        at com.petpet.c3po.command.ProfileCommand.execute(ProfileCommand.java:70)
        at com.petpet.c3po.C3PO.compute(C3PO.java:135)
        at com.petpet.c3po.C3PO.main(C3PO.java:167)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions