You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by "Weian Deng (JIRA)" <ji...@apache.org> on 2017/09/25 18:40:00 UTC

[jira] [Updated] (LOG4J2-1944) Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.

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

Weian Deng updated LOG4J2-1944:
-------------------------------
    Attachment: LOG4J2-1944.patch

> Should suppress message "ERROR No log4j2 configuration file found..." when programmatic API is used to config log4j.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1944
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1944
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>    Affects Versions: 2.6.2
>            Reporter: Weian Deng
>            Priority: Minor
>         Attachments: LOG4J2-1944.patch, LOG4J2_1944.zip
>
>
> Log4j can be configured through log4j's configuration API.  There are cases that an organization want to control the log4j configuration through the configuration API and discourage the use of config file.  The error message
> {code}
> ERROR No log4j2 configuration file found. Using default configuration: logging only errors to the console.
> {code}
> is misleading.  
> Can this be downgraded to WARN message, or provide a way to suppress it?



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