You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Piotr Karwasz (Jira)" <ji...@apache.org> on 2023/02/02 14:13:00 UTC
[jira] [Resolved] (LOG4J2-3647) Equivalence of `LogBuilder` and `Logger` calls
[ https://issues.apache.org/jira/browse/LOG4J2-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Karwasz resolved LOG4J2-3647.
-----------------------------------
Resolution: Fixed
> Equivalence of `LogBuilder` and `Logger` calls
> ----------------------------------------------
>
> Key: LOG4J2-3647
> URL: https://issues.apache.org/jira/browse/LOG4J2-3647
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: Piotr Karwasz
> Priority: Major
> Fix For: 2.20.0
>
>
> The following two calls should behave in the same way:
> {code:java}
> logger.info(marker, "Hello Log4j2 Core!");
> logger.atInfo().withMarker(marker).log("Hello Log4j2 Core!");
> {code}
> If we use global filters and the filter returns {{ACCEPT}}, the first call will log a message even if the logger's level is lower than {{INFO}}. The second call will not log anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)