-
Bug
-
Resolution: Fixed
-
P3
-
9, 10
-
b36
-
Verified
The following used to work in JDK 8:
logging.properties:
==============
.level = INFO
.handlers = java.util.logging.ConsoleHandler
==============
Test.java:
public class Test {
public static void main(String[] args) {
java.util.logging.Logger.getAnonymousLogger().info("Hi!");
}
}
but no longer woks in 9. In 9 you have to write:
logging.properties:
==============
.level = INFO
handlers = java.util.logging.ConsoleHandler
==============
(as specified in logging.properties)
This is a regression, probably introduced byJDK-8033661
logging.properties:
==============
.level = INFO
.handlers = java.util.logging.ConsoleHandler
==============
Test.java:
public class Test {
public static void main(String[] args) {
java.util.logging.Logger.getAnonymousLogger().info("Hi!");
}
}
but no longer woks in 9. In 9 you have to write:
logging.properties:
==============
.level = INFO
handlers = java.util.logging.ConsoleHandler
==============
(as specified in logging.properties)
This is a regression, probably introduced by
- relates to
-
JDK-8033661 readConfiguration does not cleanly reinitialize the logging system
-
- Resolved
-
-
JDK-8195096 Exception printed on console with custom LogManager on starting Apache Tomcat
-
- Closed
-