ppkarwasz commented on issue #3667: URL: https://github.com/apache/logging-log4j2/issues/3667#issuecomment-2886007251
> Related? #2282 Yes, you're right — that pull request is indeed responsible for the behavior change you're seeing. We were previously using the incorrect `Logger.setLevel` method internally instead of `Configurator.setLevel`. After that change, `o.a.l.Logger.setLevel` began properly re-synchronizing the cached levels of `o.a.l.l.Logger` instances with the current Configuration. Following #2778, the `log4j-1.2-api` module is no longer supposed to modify the Log4j Core configuration by default. However, it looks like we missed a few methods that still allow this. As an answer to this bug report, we should update `log4j-1.2-api` to prevent any modifications to the Core configuration unless `log4j1.compatibility` is explicitly set to `true`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
