You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2017/06/30 05:51:00 UTC

[jira] [Closed] (LOG4J2-1954) Configurations with multiple root loggers should fail loudly

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

Remko Popma closed LOG4J2-1954.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.9

Fixed in master.

> Configurations with multiple root loggers should fail loudly
> ------------------------------------------------------------
>
>                 Key: LOG4J2-1954
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1954
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>    Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>             Fix For: 2.9
>
>         Attachments: prevent-multiple-roots.png
>
>
> Log4j2 currently accepts configurations with multiple <root> elements without errors or warnings. Based on multiple questions I've seen on StackOverflow, such configurations rarely work correctly.
> During initialization, Log4j2 should detect this problem and fail with an ERROR (or FATAL) message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)