[
https://issues.apache.org/jira/browse/LOG4J2-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759237#comment-13759237
]
Ralph Goers commented on LOG4J2-394:
------------------------------------
I just recently added that code to allow a LoggerContext that was created with
no configuration to obtain one. It looks like we just need to add another check
for a null configLocation being passed in and ignore it if it is.
> ClassLoaderContextSelector logging WARN messages
> ------------------------------------------------
>
> Key: LOG4J2-394
> URL: https://issues.apache.org/jira/browse/LOG4J2-394
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Affects Versions: 2.0-beta9
> Reporter: Abhinav Shah
>
> I am getting the following WARN message everytime my application logs
> something.
> {color:red}
> WARN locateContext called with URI null. Existing LoggerContext has URI
> classpath:log4j/local.log4j.xml
> {color}
> I traced this to ClassLoaderContextSelector -
> {code}
> if (ctx != null) {
> if (ctx.getConfigLocation() == null && configLocation != null) {
> LOGGER.debug("Setting configuration to {}", configLocation);
> ctx.setConfigLocation(configLocation);
> } else if (ctx.getConfigLocation() != null &&
> !ctx.getConfigLocation().equals(configLocation)) {
> LOGGER.warn("locateContext called with URI {}. Existing
> LoggerContext has URI {}", configLocation,
> ctx.getConfigLocation());
> }
> return ctx;
> }
> {code}
> [[email protected]] [[email protected]] Why are we
> logging these WARN messages?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
