[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488581#comment-17488581
]
Duo Zhang commented on LOG4J2-3394:
-----------------------------------
Oh, wait a minute, if this feature could be done via customized configuration
factory, then why not just modify the PropertiesConfigurationFactory to support
it? It is a common usage, not only for hadoop.
You can search 'log4j configuration' on google, at least for me, the first
serveral results all tell you to use properties file and use
'log4j.rootLogger=level[, appender1, appender2…]' syntax, so I prefer we still
try to support this usage in log4j2...
Thanks.
> 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)
