You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Daniel Liu (JIRA)" <ji...@apache.org> on 2016/09/27 07:23:20 UTC
[jira] [Updated] (LOG4J2-1615) Occured again -
log4j2.component.properties not read for all properties
[ https://issues.apache.org/jira/browse/LOG4J2-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Liu updated LOG4J2-1615:
-------------------------------
Affects Version/s: (was: 2.2)
2.6.2
Fix Version/s: (was: 2.3)
Description:
Some parts of the code read System properties using System.getProperty and some do it through PropertyUtils. I've added a patch to read all config properties using PropertyUtils so that values specified in log4j2.component.properties will be honored.
I guess all this'll be obsolete if LOG4J2-321 will get done, but in the meantime it'd be nice for the code to behave the same way for all properties.
This issue occured again in 2.6.2, log4j2.component.properties not read.
was:
Some parts of the code read System properties using System.getProperty and some do it through PropertyUtils. I've added a patch to read all config properties using PropertyUtils so that values specified in log4j2.component.properties will be honored.
I guess all this'll be obsolete if LOG4J2-321 will get done, but in the meantime it'd be nice for the code to behave the same way for all properties.
> Occured again - log4j2.component.properties not read for all properties
> -----------------------------------------------------------------------
>
> Key: LOG4J2-1615
> URL: https://issues.apache.org/jira/browse/LOG4J2-1615
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.6.2
> Reporter: Daniel Liu
> Priority: Minor
>
> Some parts of the code read System properties using System.getProperty and some do it through PropertyUtils. I've added a patch to read all config properties using PropertyUtils so that values specified in log4j2.component.properties will be honored.
> I guess all this'll be obsolete if LOG4J2-321 will get done, but in the meantime it'd be nice for the code to behave the same way for all properties.
> This issue occured again in 2.6.2, log4j2.component.properties not read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org