You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/06 00:53:20 UTC
[jira] [Commented] (LOG4J2-1500) Merging configurations fail with
an NPE when comparing Nodes with different attributes
[ https://issues.apache.org/jira/browse/LOG4J2-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410346#comment-15410346 ]
ASF GitHub Bot commented on LOG4J2-1500:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/37
> Merging configurations fail with an NPE when comparing Nodes with different attributes
> --------------------------------------------------------------------------------------
>
> Key: LOG4J2-1500
> URL: https://issues.apache.org/jira/browse/LOG4J2-1500
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.6.2
> Reporter: Jose Leon
> Fix For: 2.7
>
>
> When you pass two configurations and there are different Nodes in the Root logger a NPE gets thrown.
> Example stub configuration 1
> {code:xml}
> <Loggers>
> <Root level="...">
> <AppenderRef ref="STDOUT">
> <Property name="hostname">server1</Property>
> </Root>
> </Loggers>
> {code}
> Example stub configuration 2
> {code:xml}
> <Loggers>
> <Root level="...">
> <AppenderRef ref="STDOUT">
> <AppenderRef ref="File">
> </Root>
> </Loggers>
> {code}
> Failure happens because DefaultMergeStrategy.isSameName() and isSameReference() calls get() without checking for null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org