[LOG4J2-1812] Improve error message when log4j 2 configuration file not found

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
• Fix Version/s: 2.9.0
• Component/s: Configurators
• Epic Link: Log4j2 ergonomics
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 12/Feb/17 05:15
• Updated: 25/Jun/17 01:34
• Resolved: 25/Jun/17 01:34

Description

When configuration fails because no Log4j 2 configuration file is found, the following message is logged to the console at ERROR level:

No log4j2 configuration file found. Using default configuration: logging only errors to the console.

We should be able to improve this. One idea is to add this:

No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.

Another idea is to dump the contents of the StatusLogger ring buffer to the console.

Issue Links

• relates to: LOG4J2-1431 Simplify log4j system property naming scheme