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

Update Locker _threadId when stashing/unstashing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.7.6
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2018-04-09, Storage NYC 2018-04-23
    • Linked BF Score:
      13

      Description

      For debugging, the Locker class has a _threadId member that is displayed when the lock manager dumps a lock report. To avoid confusion when using the report for diagnosis, we should ensure that this member is updated when Lockers are taken out of their originating OperationContext and stashed, and then updated again when unstashed and assigned to a new thread with a new OperationContext.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: