Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-6510

Double-Checked Locking field must be volatile

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.17.0, 5.2.0, 4.16.2, 5.1.3
    • None
    • None

    Description

      There are three places where the field used for double-checked locking isn't volatile. Change them to volatile to ensure thread-safety.

      More details on the double-checked locking paradigm: https://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html

      Attachments

        Issue Links

          Activity

            People

              weichiu Wei-Chiu Chuang
              weichiu Wei-Chiu Chuang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: