You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/04/23 22:34:00 UTC

[jira] [Resolved] (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 ]

Christopher Tubbs resolved ACCUMULO-3546.
-----------------------------------------
    Resolution: Fixed

> 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
>            Priority: Major
>             Fix For: 2.0.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
(v7.6.3#76005)