You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/04/05 07:36:34 UTC
[jira] [Updated] (ACCUMULO-3546) Log4j should be initialized using
java system properties, not code
[ https://issues.apache.org/jira/browse/ACCUMULO-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-3546:
---------------------------------
Fix Version/s: (was: 1.7.0)
1.8.0
> Log4j should be initialized using java system properties, not code
> ------------------------------------------------------------------
>
> Key: ACCUMULO-3546
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3546
> Project: Accumulo
> Issue Type: Improvement
> Reporter: Christopher Tubbs
> Fix For: 1.8.0
>
>
> Our log4j configuration files are confusing. It is not clear, unless looking at code, how our configuration files for logging are supposed to be used, and for which services.
> Even then, there are bugs, such as ACCUMULO-3544, because we assume we can log normally without first initializating the logging system.
> We should rely on log4j's default behavior to initialize the logging based on standard configuration files. If we need to specify a different file, we should do that with the java system properties that log4j supports ({{-Dlog4j=...}}) and set those in our environment scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)