https://bz.apache.org/bugzilla/show_bug.cgi?id=66406
Piotr P. Karwasz <pkarw...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Piotr P. Karwasz <pkarw...@apache.org> ---
I believe that this behavior is dictated by the lack of support in JUL for
logger contexts, which forces Tomcat to use several hacks and tricks.
However, I have to partially agree with this report. The way Tomcat JULI deals
with `Handler` sharing between applications is inconsistent. If an application
does not have a `logging.properties` file (very common case):
* the root logger of an application has the global root logger as parent and
`useParentHandlers` set to true. This way it delegates all logging to the
global root logger handlers,
* all other loggers copy the references to global handlers as their own.
I believe that this architecture can be simplified and remove the need for a
parent of the root logger. I'll try to submit a PR for it.
--
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
