[
https://issues.apache.org/jira/browse/LOG4J2-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150460#comment-17150460
]
Ralph Goers commented on LOG4J2-2882:
-------------------------------------
I guess that is understandable since we expect that only the Filters configured
on Log4j Loggers would be used.
> JUL adapter ignores log filters
> -------------------------------
>
> Key: LOG4J2-2882
> URL: https://issues.apache.org/jira/browse/LOG4J2-2882
> Project: Log4j 2
> Issue Type: Bug
> Components: JUL adapter
> Affects Versions: 2.13.3
> Environment: {{monospaced text}}
> Reporter: Emmanuel Bourg
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Setting a {{java.util.logging.Filter}} on a logger has no effect when the JUL
> adapter is used. For example with:
> {code:java}
> Logger logger = new CoreLoggerAdapter().getLogger("test");
> logger.setFilter(record -> false);
> logger.info("Test");
> {code}
> the message is still logged.
> {{org.apache.logging.log4j.jul.ApiLogger}} does check the filter in its
> {{log(LogRecord)}} method, but the other log methods bypass it and call
> directly the underlying log4j logger.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
