Reverse order of TransactionParticipant (Session in 4.0) and Client locks

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.2, 4.1.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2018-08-27
    • 46
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The Client lock is a spin lock which should be acquired last and held for as short a duration as practical. We should therefore acquire it after acquiring the TransactionParticipant mutex when changing the locker on the OperationContext.

            Assignee:
            Matthew Russotto
            Reporter:
            Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: