You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/01/10 13:09:00 UTC

[jira] [Updated] (LOG4J2-3326) Log4j 1.2 bridge not parsing filters from Properties configuration properly

     [ https://issues.apache.org/jira/browse/LOG4J2-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary D. Gregory updated LOG4J2-3326:
------------------------------------
    Summary: Log4j 1.2 bridge not parsing filters from Properties configuration properly  (was: Log4j 1.2 bridge not parsing filters from Properies configuration properly)

> Log4j 1.2 bridge not parsing filters from Properties configuration properly
> ---------------------------------------------------------------------------
>
>                 Key: LOG4J2-3326
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3326
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: log4j 1.2 emulation
>    Affects Versions: 2.17.1
>            Reporter: Benjamin Röhl
>            Assignee: Gary D. Gregory
>            Priority: Major
>
> h2. Status Quo
> The log4j 1.2 bridge gives backward-compatiblilty for the following filters, based on [migration documentation|https://logging.apache.org/log4j/2.x/manual/migration.html]:
> {code:java}
> Supported Filters include: DenyAllFilter, LevelMatchFilter, LevelRangeFilter, StringMatchFilter.{code}
> h2. Problem
> The filters' parameters are not parsed properly, and instead fallback to default configuration for filter.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)