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

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 9
    • Affects Version/s: None
    • Component/s: 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.

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

                Created:
                Updated:
                Resolved: