• Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 5.1.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Summary

      (lifted from PR description)

      This PR primarily does three things:

      • ensures that the message stream is always destroyed and ensure that the socket is always destroyed
      • consolidate the connection clean up logic into a single function that is called from each point where the connection is cleaned out
      • improves the unit tests to properly assert on the state of the connection after _cleanup has been called.
        • Additionally, the unit tests now in for synchronous versus asynchronous behavior for the various error and clean up scenarios.

            Assignee:
            bailey.pearson@mongodb.com Bailey Pearson
            Reporter:
            bailey.pearson@mongodb.com Bailey Pearson
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: