Operational Defect Database

BugZero found this defect 2506 days ago.

MongoDB | 374836

[SERVER-28830] cursorHandleFromId should verify that its not being called on a closed connection

Last update date:

1/30/2019

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.6.6

4.0.0-rc0

Description:

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

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...