[JAVA-417] When QUERYOPTION_EXHAUST is set, the Java Driver sents getMore requests, causing a failure Created: 17/Aug/11  Updated: 19/Oct/16  Resolved: 28/Aug/12

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: 2.6.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Brendan W. McAdams Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible

 Description   

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.



 Comments   
Comment by Jeffrey Yemin [ 28/Aug/12 ]

Exhaust option is no longer allowed. See commit 3cf4946fd8ef1669277fc572052b0dd7e76b2736

Generated at Thu Feb 08 08:52:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.