Executable.hasRealParameterData should not be volatile

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 20
    • Affects Version/s: None
    • Component/s: core-libs
    • None

      If there are two threads calling Executable.hasRealParameterData() under race and the first one writes into volatile Executable.parameters field (doing releasing store) and the second thread reads non-null value from the same field (doing acquiring read) then it must read exactly the same value written into hasRealParameterData within privateGetParameters().

      In the opposite case (acquiring read reads null) the second thread writes the value itself and returns it from the method.

            Assignee:
            Sergey Tsypanov
            Reporter:
            Sergey Tsypanov
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: