[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307089#comment-16307089
]
Ralph Goers commented on LOG4J2-1944:
-------------------------------------
The user is asking that the logger.error in ConfigurationFactory be changed to
a warn level message - which means it won't be printed unless a system property
has been set. Gary has suggested that the message be modified to include the
url to the Configuration page. While helpful, that really doesn't deal with the
user's request.
I have mixed feelings about this as we have had users doing programmatic
configuration not understand why this message is printing before their
configuration takes effect. I suppose an option would be to enhance to status
logger to support some sort of rudimentary filtering.
> 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)
