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

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307512#comment-16307512 ] 

Ralph Goers edited comment on LOG4J2-1944 at 1/1/18 5:41 PM:
-------------------------------------------------------------

[~mikaelstaldal] This happens any time something is logged before the configuration occurs. For example, if you try to configure Log4j from a Spring component you will get this error. The flow there is:
1. Spring servlet listener calls some Spring class.
2. The Spring class calls LogManager.getLogger().
3. Log4j generates the error.
4. Spring calls the application component that configures Log4j.


was (Author: ralph.goers@dslextreme.com):
[~mikaelstaldal] This happens any time something is logged before the configuration occurs. For example, if you try to configure Log4j from a Spring component you will get this error.

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