[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488342#comment-17488342
]
Ralph Goers edited comment on LOG4J2-3394 at 2/7/22, 7:33 PM:
--------------------------------------------------------------
This issue is marked resolved as it relates to the bug in what Matt
implemented. Matt's code is going to be removed and replaced with something
else. So LOG4J2-3341 really needs to be reopened.
[~mattsicker] After you revert the change for LOG4J2-3341 I will look into
adding the support as a "normal" property that simply performs two different
actions. it does mean that if you do
{code:java}
rootLogger=${sys:root.logger:-INFO,console} {code}
and then define the root.logger system property as something like:
{code:java}
${sys:log.level:-INFO}, console
{code}
The log level info replacement will not occur. Instead, it will get an error
when it tries to set the level to "${sys:log.level:-INFO}".
was (Author: [email protected]):
This issue is marked resolved as it relates to the bug in what Matt
implemented. Matt's code is going to be removed and replaced with something
else. So LOG4J2-3341 really needs to be reopened.
> The 'rootLogger=${sys:root.logger:-INFO,console}' does not work
> ---------------------------------------------------------------
>
> Key: LOG4J2-3394
> URL: https://issues.apache.org/jira/browse/LOG4J2-3394
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration
> Reporter: Duo Zhang
> Priority: Major
> Attachments: log4j2.err, log4j2.properties
>
>
> Tried the new feature introduced in LOG4J2-3341 in hbase.
> https://github.com/apache/hbase/pull/4096
> I built a tarball and try to start a standalone hbase instance locally, but
> log4j2 failed to load the system properties of rootLogger.
> Will upload the config and error output.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
