https://bz.apache.org/bugzilla/show_bug.cgi?id=66406
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
Tomcat JULI is explicitly intended to permit multiple loggers with the same
name.
Consider the case where different applications using the same library are
deployed to a Tomcat instance. If that library uses java.util logging, the
applications will share loggers making it difficult/impossible to identify
which messages originate from which application.
JULI solves this problem by extending the unique key for a logger from name to
class loader + name. Since each web application has a dedicated class loader,
loggers for each web application remain separate - even if both applications
have a logger with the same name.
The description in comment #1 of how the handlers are configured does not match
what I see with the current code.
Given that there is one root logger (called "") per class loader and that the
requirement is for logging to be delegated to the parent class loader's
handlers if the current class loader doesn't have an explicit configuration, I
don't see how the current setup could be simplified but I'll leave this issue
open for now as it is always possible there is a solution I haven't thought
of.
I am changing this to an enhancement request though as having multiple loggers
with the same name, including the root loggers, is by design.
--
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
