You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2014/08/06 16:44:12 UTC

[jira] [Resolved] (LOG4J2-729) Emit warning message to console if no config file found

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

Remko Popma resolved LOG4J2-729.
--------------------------------

    Resolution: Fixed

Log4j2 will now emit the following warning message to System.err if no configuration file was found:

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

Fixed in revision 1616252.
Please verify and close

> Emit warning message to console if no config file found
> -------------------------------------------------------
>
>                 Key: LOG4J2-729
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-729
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>            Reporter: Cyrille Karmann
>            Assignee: Remko Popma
>            Priority: Minor
>             Fix For: 2.0.2
>
>
> In a situation where no Jackson library has been added to the classpath of the project, if there is a log4j2.json file, the logger will silently use the default configuration, ignoring any log4j2.xml file that would also be available in the project.
> Instead, log4j should either use the log4j2.xml file for configuration, or some error message should be displayed, to show that log4j2.json could not be read, and that the default configuration is used.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org