[
https://issues.apache.org/jira/browse/ACCUMULO-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3544.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
log4j configuration dramatically simplified in 2.0, and fixes this.
> 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
> Priority: Major
> Fix For: 2.0.0
>
>
> 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
(v7.6.3#76005)
