[
https://issues.apache.org/jira/browse/LOG4J2-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471985#comment-17471985
]
ASF subversion and git services commented on LOG4J2-3326:
---------------------------------------------------------
Commit acb671d8d265bbb49ca23f230ca7d1c744a6e2d2 in logging-log4j2's branch
refs/heads/release-2.x from benjaminr-ps
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=acb671d ]
[LOG4J2-3326] Fix parsing filters from Log4j 1.2 properties configuration file
(#680)
* Use specific filter key as prefix while parsing configuration
Problem: The log4j 1.x configuration file is not properly parsed, in regards of
filters. Whatever is configured in file, is getting ignored, and default values
are used.
E.g. for "level range filter" the LevelMax is not properly found (eventhough
properly read as property).
Root cause: The default filter prefix is used, instead of specific filter key.
* add test, verifying LevelRangeFilter properly parsed/configured
...with values of properties configuration file
> 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)
