[ACCUMULO-3546] Log4j should be initialized using java system properties, not code

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Assignee: Unassigned
• Reporter: Christopher Tubbs
• Created: 29/Jan/15 22:44
• Updated: 23/Apr/19 22:33
• Resolved: 23/Apr/19 22:33

Description

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.

Issue Links

• is related to: ACCUMULO-2349 Accumulo should give some notification if there is no *_logger.xml file
• relates to: ACCUMULO-3544 accumulo-start uses log4j before it is initialized
• relates to: ACCUMULO-3955 switch off of log4j v1.x
• supercedes: ACCUMULO-2954 Clarify properties vs. xml precedence for generic_logger and monitor_logger