[
https://issues.apache.org/jira/browse/LOG4J2-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453771#comment-17453771
]
ASF subversion and git services commented on LOG4J2-3166:
---------------------------------------------------------
Commit 250521073200102c8322705a17c9375b894e3941 in logging-log4j2's branch
refs/heads/release-2.x from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=2505210 ]
LOG4J2-3166 - Fix log event Level vs LoggerConfig Level table.
> 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.20.1#820001)
