[jira] [Commented] (ACCUMULO-3544) accumulo-start uses log4j before it is initialized

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ACCUMULO-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523467#comment-14523467 ] 

Christopher Tubbs commented on ACCUMULO-3544:
---------------------------------------------

One thing it looks like we should have been using since we initialize log4j ourselves, is:

{code}
-Dlog4j.defaultInitOverride=true
{code}

(from https://logging.apache.org/log4j/1.2/manual.html#Default_Initialization_Procedure)

However, we can't really do that with the accumulo-start logging.

> accumulo-start uses log4j before it is initialized
> --------------------------------------------------
>
>                 Key: ACCUMULO-3544
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3544
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>            Reporter: Christopher Tubbs
>
> Classes in the accumulo-start module appear to incorrectly use the log4j system before it is properly initialized.
> ACCUMULO-2628 appears to have introduced it to start's Main class, but it looks like it's been around awhile in the AccumuloClassLoader and the new vfs class loader.
> The output of these loggers will probably not go where we expect them to go, based on our custom log4j configuration files... certainly not before we execute the code to initialize log4j based on those configuration files. Hopefully, they will default to the console logger and get logged to the .out and .err files, but if there's a log4j.properties or log4j.xml file in the classpath, they could redirect these errors to somewhere else and we may not see them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)