Update Locker _threadId when stashing/unstashing

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.6
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-04-09, Storage NYC 2018-04-23
    • 13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            James Wahlin
            Reporter:
            Eric Milkie
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: