Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-1096

When limit is set with a BatchCursor connected to a legacy server, a connection is leaked

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.4
    • Component/s: Core API
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible

      Description

      In the legacyGetMore method on driverlegacy.BatchCursor, when we reach the limit set by the user we fail to close the connection we opened. This can be fixed by moving the code that checks the limit before we retrieve a connection from the BatchCursor's server.

      Since driverlegacy will be removed soon (in the master branch), this fix should only be done on the release/1.0 branch.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: