[
https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488587#comment-17488587
]
Duo Zhang commented on LOG4J2-3394:
-----------------------------------
Yes, for this we are on the same page. I agree that we should not do this if it
breaks some assumptions in log4j, please see my comment above.
So now the problem is how to implement with other ways. Inside log4j, using
CompoundProperty and appenderRefs is a possible way, and another proposed
approach is to use a customized configuration factory. I'm still learning from
the code and documentation, and one querstion is as I said above, if it could
be done via customized configuration factory, then why we can not support it by
modifying the PropertiesConfigurationFactory?
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)
