[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055313#comment-16055313
]
Pierrick HYMBERT commented on LOG4J2-1944:
------------------------------------------
Can you please describe how your are getting your LoggerContext via
configuration API? Better to attach a simple test case.
If you are calling
{{org.apache.logging.log4j.core.config.Configurator.initialize(org.apache.logging.log4j.core.config.Configuration)}}
and
{{org.apache.logging.log4j.core.config.builder.api.ConfigurationBuilderFactory}}
this message would not appear.
> 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
>
> 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)
