[
https://issues.apache.org/jira/browse/LOG4J2-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443561#comment-16443561
]
ASF GitHub Bot commented on LOG4J2-2321:
----------------------------------------
GitHub user cakofony opened a pull request:
https://github.com/apache/logging-log4j2/pull/169
[LOG4J2-2321] 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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-2321
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/169.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #169
----
commit 3355866e658a56da9a5796a8ffb52e3a7f020eb0
Author: Carter Kozak <ckozak@...>
Date: 2018-04-19T04:15:39Z
[LOG4J2-2321] 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.
----
> AsyncLoggerConfig default level differs from LoggerConfig
> ---------------------------------------------------------
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
