[
https://issues.apache.org/jira/browse/LOG4J2-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419805#comment-17419805
]
Georg Sonnefeld edited comment on LOG4J2-3166 at 9/24/21, 3:01 PM:
-------------------------------------------------------------------
This is logically equivalent to the behavior described in LOG4J2-3151 and
LOG4J2-2174.
Thus, I am aware of the logic in the internal filter method. The
documentation, on the other hand, put me on the wrong track of how to use the
levels.
was (Author: gson):
This is logically equivalent to the behavior described in LOG4J2-2174.
Thus, I am aware of the logic in the internal filter method. The documentation,
on the other hand, put me on the wrong track of how to use the levels.
> wrong documentation for logging with Level.OFF
> ----------------------------------------------
>
> Key: LOG4J2-3166
> URL: https://issues.apache.org/jira/browse/LOG4J2-3166
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.14.1
> Reporter: Georg Sonnefeld
> Priority: Minor
>
> The documentation states that log events of level OFF should never be logged,
> whereas level ALL should always be logged.
> See the last table in section "LoggerConfig" here:
> https://logging.apache.org/log4j/2.0/manual/architecture.html
> In fact the opposite is the case.
> The following statement in combination with the default configuration leads
> to a log entry.
> {code:java}
> LogManager.getLogger().log(Level.OFF, "test");{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
