Info

The old implementation of DBCommandCursor used when running the shell with --readMode compatibility calls getConnection(which checks if the connection has been closed) to construct a DBClientCursor which it passes to setCursor. The new variant used with --readMode command calls setCursorHandle with the cursor ID. This new variant doesn't check if the connection has been closed.

Top User Comments

xgen-internal-githook commented on Tue, 22 May 2018 17:17:33 +0000: Author: {'username': 'hanumantmk', 'name': 'Jason Carey', 'email': 'jcarey@argv.me'} Message: SERVER-28830 check for closed conn in cursorHandleFromId The old implementation of DBCommandCursor used when running the shell with --readMode compatibility calls getConnection(which checks if the connection has been closed) to construct a DBClientCursor which it passes to setCursor. The new variant used with --readMode command calls setCursorHandle with the cursor ID. Check that we aren't closed in the new variant. (cherry picked from commit bb2a2ccf260929e8a97080f81cd696340d429d57) Branch: v3.6 https://github.com/mongodb/mongo/commit/c3c9a3a04c47e08054b224e167373c6f46112f8c xgen-internal-githook commented on Thu, 3 May 2018 17:38:00 +0000: Author: {'email': 'jcarey@argv.me', 'name': 'Jason Carey', 'username': 'hanumantmk'} Message: SERVER-28830 check for closed conn in cursorHandleFromId The old implementation of DBCommandCursor used when running the shell with --readMode compatibility calls getConnection(which checks if the connection has been closed) to construct a DBClientCursor which it passes to setCursor. The new variant used with --readMode command calls setCursorHandle with the cursor ID. Check that we aren't closed in the new variant. Branch: master https://github.com/mongodb/mongo/commit/bb2a2ccf260929e8a97080f81cd696340d429d57

Steps to Reproduce