You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@logging.apache.org by gg...@apache.org on 2022/01/12 13:09:15 UTC

[logging-log4j2] 03/03: [LOG4J2-3330] Configurator.setLevel not fetching the correct LoggerContext.

This is an automated email from the ASF dual-hosted git repository.

ggregory pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 8a77923fb8f451dc1f3e52c6e64e154c8bc2bcba
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Wed Jan 12 08:09:09 2022 -0500

    [LOG4J2-3330] Configurator.setLevel not fetching the correct
    LoggerContext.
---
 src/changes/changes.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index dcc2d67..ee1978c 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -127,6 +127,9 @@
       <action dev="ggregory" type="fix">
         JndiManager reverts to 2.17.0 behavior: Read the system property for each call.
       </action>
+      <action dev="ggregory" type="fix" issue="LOG4J2-3330" due-to="Mircea Lemnaru, Gary Gregory">
+        Configurator.setLevel not fetching the correct LoggerContext.
+      </action>
       <!-- ADD -->
       <action issue="LOG4J2-3282" dev="ckozak" type="add" due-to="Michael Vorburger">
         Add the log4j-to-jul JDK Logging Bridge