You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2023/01/02 06:31:00 UTC
[jira] [Updated] (LOG4J2-3634) Log4JBridgeHandler & Tomcat Webapps: Propagating log levels leads to no handlers in the (root) logger
[ https://issues.apache.org/jira/browse/LOG4J2-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Karwasz updated LOG4J2-3634:
----------------------------------
Fix Version/s: 2.20.0
(was: 2.19.1)
> Log4JBridgeHandler & Tomcat Webapps: Propagating log levels leads to no handlers in the (root) logger
> -----------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3634
> URL: https://issues.apache.org/jira/browse/LOG4J2-3634
> Project: Log4j 2
> Issue Type: Bug
> Components: JUL adapter
> Affects Versions: 2.19.0
> Environment: Apache Tomcat 9.0.68
> JDK Corretto 18
> macOS 12.6.1 aarch64
> Reporter: Marcel Koch
> Assignee: Piotr Karwasz
> Priority: Minor
> Fix For: 2.20.0
>
>
> In short: The loggers are altered before the handlers are added to the (root) logger. This leads to propers loggers but without any handler.
> My idea would be to move the propagation to a later point in time. So, I moved it to the method {{{}publish(){}}}.
> Here is demo repo to reproduce the issue: [https://github.com/mknet/tomcat-webapp-log4j-jul-bridge]
> Here is the Pull Request with my approach to fix the issue: [https://github.com/apache/logging-log4j2/pull/1140]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)