You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "yankai zhang (Jira)" <ji...@apache.org> on 2021/10/19 12:39:00 UTC

[jira] [Updated] (LOG4J2-3178) DefaultMergeStrategy do not merge type of logger node

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

yankai zhang updated LOG4J2-3178:
---------------------------------
    Description: 
This is how {{DefaultMergeStrategy#mergConfigurations}} merge logger nodes:

!image-2021-10-19-20-25-16-215.png|width=825,height=648!

{{type}} of the later logger node will not replace previous one.

So, if previous file define a sync root logger, and later file define an async root logger, the final logger is sync.

  was:
This is how {{DefaultMergeStrategy#mergConfigurations}} merge logger nodes:

!image-2021-10-19-20-25-16-215.png!

{{type}} of the later logger node will not replace previous one.

So, if previous file define a sync root logger, and later file define an async root logger, the final logger is sync.


> DefaultMergeStrategy do not merge type of logger node
> -----------------------------------------------------
>
>                 Key: LOG4J2-3178
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3178
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.11.1
>            Reporter: yankai zhang
>            Priority: Major
>         Attachments: image-2021-10-19-20-25-16-215.png
>
>
> This is how {{DefaultMergeStrategy#mergConfigurations}} merge logger nodes:
> !image-2021-10-19-20-25-16-215.png|width=825,height=648!
> {{type}} of the later logger node will not replace previous one.
> So, if previous file define a sync root logger, and later file define an async root logger, the final logger is sync.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)