-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b66
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084931 | emb-9 | Peter Levart | P4 | Resolved | Fixed | team |
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.
- backported by
-
JDK-8084931 Improve locking strategy for readConfiguration(), reset(), and initializeGlobalHandlers()
-
- Resolved
-
- relates to
-
JDK-8132550 java/util/logging/LoggingDeadlock2.java times out
-
- Closed
-