J.u.logging uses j.t.Instant to store LogRecord time stamps. XMLFormatter format is updated to allow for a new optional <nanos> element containing a nano second adjustment. SimpleFormatter passes a ZonedDateTime object to String.format. LogRecord getMillis/setMillis are deprecated, replaced by getInstant/setInstant.
Co-authored-by: Peter Levart <peter.levart@gmail.com>
Reviewed-by: scolebourne, plevart, rriggs
Loggers which have been configured with a handler in the configuration file will be retained by the LogManager until reset() is called. A new configuration property is added to explicitely turn the fix off.
Reviewed-by: mchung
FileHandler now uses 'long' for limit and MeteredStream.written. It also reads a long for limit from the configuration, and has a new constructor allowing to pass a 'long' for limit.
Reviewed-by: alanb, igerasim, mchung
NPE may be thrown when Path.getParentPath() returns null. The fix is to call Path.getAbsolutePath().getParentPath() when Path.getParentPath() returns null.
Reviewed-by: alanb
Added two new methods to LogManager (addConfigurationListener/removeConfigurationListener) which provide an equivalent functionality with no ties to java.beans.
Reviewed-by: alanb, mchung, plevart, psandoz
CheckZombieLockTest and CheckLockLocationTest should work with different temporary log directories so that they can be run concurrently. This fix changes the name of the log directory used by CheckZombieLockTest.
Reviewed-by: mchung
This is due to a race condition in the test where one GetRB thread can receive a stale LogRecord comming from another GetRB thread.
Reviewed-by: dholmes
In some circumstances j.u.l.FileHandler can leave zombie lock files on the file system. The fix lets FileHandler reuse such zombie lock files when it sees them - as it used to do in version 1.7 of the JDK.
Reviewed-by: alanb
The test was not keeping any strong reference on the loggers it created allowing for them to be garbage collected too early.
Reviewed-by: mchung, chegar
8029781: Theoretical data race on java.util.logging.Handler.sealed
Use privileged actions instead of racy boolean field to elevate privilege when constructing logging handlers
Reviewed-by: mchung, dfuchs
This is a test bug - loggers held in local variables can be arbitrarily gc'ed if that variable is no longer used. The fix makes sure that the loggers won't be arbitrarily gc'ed before the test is complete.
Reviewed-by: mchung
This test has been seen failing on Solaris 10, presumably because it was run as root. The fix will skip the non-writable case if it can't make a non-writable dir.
Reviewed-by: mchung
4814565: (rb) add method to get basename from a ResourceBundle
Adds Logger.setResourceBundle(ResourceBundle) and ResourceBundle.getBaseBundleName()
Reviewed-by: mchung, naoto
Arbitrary timeouts in the tests @run lines where too agressive for some configurations. The tests will now run with default timeout.
Reviewed-by: alanb, mchung
8021003: java/util/logging/Logger/getGlobal/TestGetGlobalConcurrent.java fails intermittently
8019945: test/java/util/logging/LogManagerInstanceTest.java failing intermittently
This fix untangles the class initialization of Logger and LogManager, and also cleans up the relationship between LogManager, LoggerContext, and Logger, which were at the root cause of some intermittent test failures.
Reviewed-by: mchung, martin, plevart
Break logging and AWT circular dependency, which was at the root cause for 8023258 - Logger.getLogger() after ImageIO.read() returns different logger instance
Reviewed-by: mchung, art
8024131: Issues with cached localizedLevelName in java.util.logging.Level
This fix updates logging.properties resource bundles to follow internationalization guidelines. It also fixes a caching issue with localizedLevelName. The regression test that was added needs both fixes to pass.
Reviewed-by: mchung, alanb
Due to subtle synchronization issues between LogManager & Logger class initialization the global logger doesn't have its 'manager' field initialized until the LogManager is initialized. This fix will ensure that the global logger has its 'manager' field set when getGlobal() is called.
Reviewed-by: mchung, plevart
