[
https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973269#comment-13973269
]
Matt Sicker commented on LOG4J2-607:
------------------------------------
If you run the CustomConfigurationTest, you'll see the following in the log:
{quote}
ERROR Invalid status level specified: ${sys:log4j.level}. Defaulting to ERROR.
{quote}
I'm updating the unit test to reflect the expected behavior. The test was
trying to use the ERROR level, but that's the default, so I'm switching that
and adding a check. The test currently doesn't pass, but it's related to this
bug.
> log4j2 json files do not support property substitutions
> -------------------------------------------------------
>
> Key: LOG4J2-607
> URL: https://issues.apache.org/jira/browse/LOG4J2-607
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0-rc1, 2.0-rc2
> Environment: Windows 7, JVM 7, Tomcat 7. Also tested using Mac OS X
> and JVM 8 (Tomcat 7).
> Reporter: Sebastian Audet
> Attachments: log4j2.json
>
>
> Using Property substitution in the latest release candidate doesn't work in
> JSON configuration files.
> Seems to work fine in XML files though - suggest actually parsing the results
> of the JSON file configurations?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
