You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Abhinav Shah (JIRA)" <ji...@apache.org> on 2013/09/05 18:48:52 UTC
[jira] [Created] (LOG4J2-394) ClassLoaderContextSelector logging
WARN messages
Abhinav Shah created LOG4J2-394:
-----------------------------------
Summary: 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}
--
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org