[
https://issues.apache.org/jira/browse/LOG4J2-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307513#comment-16307513
]
Mikael Ståldal commented on LOG4J2-1944:
----------------------------------------
I think it is appropriate to issue an error message when the user do not
configure Log4j at all (neither config file, nor programmatic API). Although it
would be useful to reformulate the error message to say that Log4j can be
configured either through config file or through programmatic API, and include
a link to configuration docs as [~garydgregory] suggested.
But it would be good to suppress the message when Log4j is configured through
the programmatic API (as the title of this issue says).
I don't think the message should be downgraded to warn level.
> 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)
