https://bz.apache.org/bugzilla/show_bug.cgi?id=66406
Bug ID: 66406
Summary: JULI ClassLoaderLogManager creates multiple loggers
named ""
Product: Tomcat 10
Version: unspecified
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: tomcat-...@matthew.matera.net.au
Target Milestone: --
When enabling ClassLoaderLogManager, the top of the logger are three instances
of ClassLoaderLogManager$RootLogger - all named "".
Whilst I can't point to anything in the spec to say that Loggers must be
uniquely named, the implementation of java.util.LogManager's getLogger() (via
LoggerContext.findLogger()) itself uses a HashMap to lookup Logger instances by
name. That might suggest that ClassLoaderLogManager's behaviour is, at
minimum, unexpected.
I found this situation when attempting to use Log4J's Log4jBridgeHandler and
found my logs were getting published twice: the duplicate Loggers foiled
Log4jBridgeHandler's logic in trying to remove existing handlers on the JULI
Root Logger.
--
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
