You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Mikael Ståldal (JIRA)" <ji...@apache.org> on 2018/01/01 17:35:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16307508#comment-16307508 ] 

Mikael Ståldal commented on LOG4J2-1944:
----------------------------------------

[~weiand] Can you provide an example on how you use the programmatic API to configure Log4j, and still get this error message? In your example, you do not configure Log4j at all.

> 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)