https://bz.apache.org/bugzilla/show_bug.cgi?id=66184
--- Comment #2 from Piotr P. Karwasz <pkarw...@apache.org> --- Hi Christopher, (In reply to Christopher Schultz from comment #1) > Sounds like a bug in Java, not Tomcat. > > Do you have a stack trace from where Tomcat triggers this? The `LogManager` in JDK8 initializes the level of the root logger in `LogManager#ensureLogManagerInitialized()`, so it is not a Java bug: https://github.com/openjdk/jdk8u/blob/3dca446d440e55cbb7dc3555392f4520ec9ff3bc/jdk/src/share/classes/java/util/logging/LogManager.java#L350 Tomcat's `ClassLoaderLogManager` creates additional "root" loggers (one per classloader) and: * if the classloader does not contain a `logging.properties` resource, its root logger becomes a child of its parent classloader root logger, * otherwise the root classloader remains without a parent and without a level. I have submitted a PR with a test case: https://github.com/apache/tomcat/pull/533 The lack of a `Level` object does not prevent JUL from working, since the (inaccessible) effective int level is computed correctly. However this causes problems in code that need to access the effective level like this one: https://issues.apache.org/jira/browse/LOG4J2-3564 -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
