[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405870#comment-17405870
]
Nils Breunese commented on LOG4J2-3151:
---------------------------------------
[~rgoers] In our actual application we didn't use {{Level.OFF}} directly for
logging, but the log level was set via application configuration and whatever
the user configured then gets used for the {{logger.atLevel(Level).log(...)}}
call. In this case a user set the level to {{OFF}}, expecting the logging to be
turned off for this particular class, but that is actually not what happened.
So, now our application needs to add checking code, to not call
{{logger.atLevel(Level).log(...)}} if the user configured the level to be
{{OFF}}.
> Messages get logged at level OFF
> --------------------------------
>
> Key: LOG4J2-3151
> URL: https://issues.apache.org/jira/browse/LOG4J2-3151
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.14.1
> Reporter: Nils Breunese
> Priority: Major
>
> I am using the following Log4j API to log messages at a configurable level:
> {code:java}
> logger.atLevel(level).log(...); {code}
> This works fine, but then a user configured the log level to be {{Level.OFF}}
> and to his surprise messages were still logged, at level {{OFF}}. This feels
> like a bug to me.
> I have created a small demo project that reproduces this behaviour at
> [https://github.com/breun/log4j-off]. This project logs these two messages:
> {code:java}
> INFO - Foo
> OFF - Foo {code}
> But I expected only the first of those two to get logged.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
