[
https://issues.apache.org/jira/browse/LOG4J2-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444145#comment-16444145
]
Gary Gregory commented on LOG4J2-2321:
--------------------------------------
Gotcha. Thank you for the example.
> 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
>
> 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)
