When a user sets DBCursor option QUERYOPTION_EXHAUST, after forwarding the exhaust request to the MongoDB server, the Java Driver continues making getMore calls.

This causes a failure, as Mongo is streaming back multiple reply packets automatically and the java driver is expecting a reply to a getMore, where the responseTo ID in the next packet to come in is an automatic exhaust reply which does NOT have the expected responseTo.

We need to disable calling getMore (and lock the connection from any other requests temporarily) when EXHAUST is set.