[
https://issues.apache.org/jira/browse/LOG4J2-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405709#comment-17405709
]
Volkan Yazici commented on LOG4J2-3151:
---------------------------------------
[~rgoers], I agree that {{OFF}} and {{ALL}} are special levels aimed to be used
in configuration files, not while logging. Yet they are valid logging levels
and I can find neither in the manual, nor in the javadocs mention of their
special behavior. In this regard, I agree with [~breun] that
{{logger.atLevel(OFF)}} should not get logged at all. This also brings a
follow-up question: Should {{logger.atLevel(ALL)}} be logged? I guess... yes.
IMHO, in an ideal world, {{OFF}} and {{ALL}} should not be part of {{Level}} or
at least have an indication that they are not supported while logging.
> 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)
