[ https://issues.apache.org/jira/browse/LOG4J2-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488438#comment-17488438 ]
Matt Sicker commented on LOG4J2-3394: ------------------------------------- Based on existing extension points, a custom ConfigurationFactory could theoretically be introduced at any time since 2.0. That's how programmatic configuration typically works, too (setting a custom factory with your configuration builder class). The CompoundProperty concept might work, though it smells like slowly introducing another type of expression language in the config file format. > 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)