[
https://issues.apache.org/jira/browse/LOG4J2-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069535#comment-16069535
]
ASF subversion and git services commented on LOG4J2-1954:
---------------------------------------------------------
Commit 10ad73fbce5b10df4b94986f9058164bf291cbc9 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=10ad73f ]
LOG4J2-1954 Configurations with multiple root loggers now fail loudly.
> 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)
