[LOG4J2-394] ClassLoaderContextSelector logging WARN messages

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9
• Component/s: Configurators
• Assignee: Ralph Goers
• Reporter: Abhinav Shah
• Created: 05/Sep/13 16:48
• Updated: 04/Jan/14 21:54
• Resolved: 04/Jan/14 21:54

Description

I am getting the following WARN message everytime my application logs something.

WARN locateContext called with URI null. Existing LoggerContext has URI classpath:log4j/local.log4j.xml

I traced this to ClassLoaderContextSelector -

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;
        }

[e-mail] [e-mail] Why are we logging these WARN messages?

Issue Links

• is related to: LOG4J2-293 classloader URI scheme broken or insufficient when using Log4jContextListener