Details
-
Bug
-
Resolution: Fixed
-
P3
-
7-pool, 8
-
None
-
b108
-
Verified
Description
LogManager class initialization is fragile: because Logger constructor calls LogManager.getLogManager, and because LogManager calls new Logger during LogManager class initialization, and because the global logger is instantiated during Logger class initialization, loading Logger.class or LogManager.class can lead to challenging issues (see for instance JDK-8021003).
It would be good if the root and global logger could be lazily added to LogManager, so that loading LogManager.class doesn't create instances of Logger.
It would be good if the root and global logger could be lazily added to LogManager, so that loading LogManager.class doesn't create instances of Logger.
Attachments
Issue Links
- relates to
-
JDK-7093220 java/util/logging/ParentLoggersTest.java fails for agentvm mode on solaris-x64 and solaris-sparcv9
- Closed
-
JDK-8019945 test/java/util/logging/LogManagerInstanceTest.java failing intermittently
- Closed
-
JDK-8021003 java/util/logging/Logger/getGlobal/TestGetGlobalConcurrent.java fails intermittently
- Closed
-
JDK-7184195 java.util.logging.Logger.getGlobal().info() doesn't log without configuration
- Closed