Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45276

Release lock before destroying DBClientBases

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Networking, Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • 21

      An error occurs in testing because DBConnectionPool acquires its mutex (declared here at acquisition level 0) in this function which eventually tries to acquire this latch which was declared here at lock level 0, causing an InvalidWasPresent error. We should reconsider the lock level in DBConnectionPool maybe, or reconsider whether it is necessary to have a mutex in ConnectionShardStatus.

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: