java.util.logging.Logger.getGlobal().info() doesn't log without configuration (original) (raw)
Jim Gish jim.gish at oracle.com
Wed Apr 24 21:23:00 UTC 2013
- Previous message: hg: jdk8/tl/jdk: 8005555: TEST_BUG: java/io/Serializable/accessConstants/AccessConstants.java should be removed
- Next message: hg: jdk8/tl/jdk: 8012638: test/java/time/test/java/util/TestFormatter fails in UTC TZ
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Please review http://cr.openjdk.java.net/~jgish/Bug7184195-global-logger-failure.1/ <http://cr.openjdk.java.net/%7Ejgish/Bug7184195-global-logger-failure.1/>
This is a simple fix that removes a long-standing bug in acquiring a using the global Logger in which Logger.getGlobal().info() (for example), would not log without additional configuration that would trigger LogManager initialization. I have also added a test to reassure us that I have not introduced a deadlock between LogManager initialization and getting the global logger.
In addition, I've introduced a utility class I developed during a recent fix to a logging deadlock, which helps us detect and report on the details of a deadlock.
Thanks, Jim
-- Jim Gish | Consulting Member of Technical Staff | +1.781.442.0304 Oracle Java Platform Group | Core Libraries Team 35 Network Drive Burlington, MA 01803 jim.gish at oracle.com
- Previous message: hg: jdk8/tl/jdk: 8005555: TEST_BUG: java/io/Serializable/accessConstants/AccessConstants.java should be removed
- Next message: hg: jdk8/tl/jdk: 8012638: test/java/time/test/java/util/TestFormatter fails in UTC TZ
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]