You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2017/06/25 01:35:02 UTC

[jira] [Resolved] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

     [ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma resolved LOG4J2-1812.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.9

Closing this ticket since the title issue has been addressed.

> Improve error message when log4j 2 configuration file not found
> ---------------------------------------------------------------
>
>                 Key: LOG4J2-1812
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1812
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Configurators
>    Affects Versions: 2.3, 2.4, 2.5, 2.6, 2.7, 2.8
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>             Fix For: 2.9
>
>         Attachments: LOG4J2_1801_Add_more_detail_to_WARN__Ignoring_log_event__messages_printed_to_the_console_a.patch
>
>
> When configuration fails because no Log4j 2 configuration file is found, the following message is logged to the console at ERROR level: 
> {code}
> No log4j2 configuration file found. Using default configuration: logging only errors to the console.
> {code}
> We should be able to improve this. One idea is to add this:
> {code}
> 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.
> {code}
> Another idea is to dump the contents of the StatusLogger ring buffer to the console.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)