Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8077846

Improve locking strategy for readConfiguration(), reset(), and initializeGlobalHandlers()

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 9
    • None
    • core-libs

        The current locking strategy for readConfiguration(), reset(), and initializeGlobalHandlers() use multiple synchronization blocks to lock partial critical sections. Using a reantrant lock object could make it possible to remove most of the synchronized blocks on LogManager, and initializeGlobalHandlers() could then be improved to avoid contention when global handlers are already initialized.

              dfuchs Daniel Fuchs
              dfuchs Daniel Fuchs
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: