[
https://issues.apache.org/jira/browse/LOG4J2-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449864#comment-16449864
]
ASF subversion and git services commented on LOG4J2-2321:
---------------------------------------------------------
Commit 59c88823737a824d3aae0f39ad2d5db570250160 in logging-log4j2's branch
refs/heads/release-2.x from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=59c8882 ]
[LOG4J2-2321] AsyncLogger uses the parent level when unspecified
AsyncLoggerConfig is parsed the same way as LoggerConfig.
When level is not specified on an AsyncLogger it is inherited from
the parent rather than set to ERROR, this provides parity with
the standard LoggerConfig.
> AsyncLogger without specifying a level always uses ERROR
> --------------------------------------------------------
>
> Key: LOG4J2-2321
> URL: https://issues.apache.org/jira/browse/LOG4J2-2321
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.11.0
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 3.0.0
>
>
> An AsyncLogger definitions without a level defined always have "ERROR" level
> set, where Logger definitions defer to the parent config, error is only set
> for the root logger.
> For example:
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <Configuration>
> <Appenders>
> <Null name="null"/>
> </Appenders>
> <Loggers>
> <AsyncLogger name="com.foo" />
> <AsyncRoot level="trace">
> <AppenderRef ref="null" />
> </AsyncRoot>
> </Loggers>
> </Configuration>{noformat}
> Logger "com.foo" level should be trace, inherited from the root logger,
> however it will currently be error.
> The same config using "Logger" and "Root" rather than their asynchronous
> counterparts will produce the expected behavior.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
