Commit Graph

8 Commits

Author SHA1 Message Date
Daniel Fuchs
9183fba213 8028788: Logger.enterring uses String concatenation in a loop
Changed code to use StringBuilder instead.

Reviewed-by: chegar, lancea
2014-10-07 14:49:45 +02:00
Daniel Fuchs
2be7f4fdda 8030187: TEST_BUG: java/util/logging/Logger/setResourceBundle/TestSetResourceBundle.java failing again
Yet another issue with Loggers being gc'ed too early.

Reviewed-by: mchung
2013-12-20 14:53:38 +01:00
Daniel Fuchs
9ef30e9ae7 8013839: Enhance Logger API for handling of resource bundles
4814565: (rb) add method to get basename from a ResourceBundle

Adds Logger.setResourceBundle(ResourceBundle) and ResourceBundle.getBaseBundleName()

Reviewed-by: mchung, naoto
2013-10-16 20:47:30 +02:00
Daniel Fuchs
ddddd1d31f 8025140: TEST_BUG: java/util/logging/Logger/getGlobal tests fail due to timeout
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
2013-09-25 09:47:24 +02:00
Daniel Fuchs
f0317e41c1 8024525: Make Logger log methods call isLoggable()
This changeset makes the various Logger logging method call isLoggable() instead of inlining the level checks.

Reviewed-by: mchung, alanb
2013-09-12 17:01:39 +02:00
Daniel Fuchs
33dbc2d51c 8023168: Cleanup LogManager class initialization and LogManager/LoggerContext relationship
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
2013-09-09 13:59:51 +02:00
Daniel Fuchs
6d2de008d7 8005899: Logger.getLogger(name, null) should not allow to reset a non-null resource bundle
Reviewed-by: mchung, lancea
2013-08-23 20:59:34 +02:00
Daniel Fuchs
5f717a6674 7184195: java.util.logging.Logger.getGlobal().info() doesn't log without configuration
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
2013-07-02 19:47:58 +02:00