[LOG4J2-293] classloader URI scheme broken or insufficient when using Log4jContextListener

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta7
• Fix Version/s: 2.0-beta9
• Component/s: Configurators
• Labels: documentation
• Assignee: Nick Williams
• Reporter: Neale Upstone
• Created: 23/Jun/13 14:34
• Updated: 05/Sep/13 17:14
• Resolved: 02/Sep/13 04:22

Description

I'm trying to migrate to Log4j2, and things looked promising when I spotted Log4jContextListener.

However, there are too many holes.

Firstly, I tried using classpath: as a scheme, and nothing blew up, so I assumed I'd got it right.

Then I looked at the code (which shouldn't be how we find out) and eventually discovered some code relating to a 'classloader' scheme.

Still silent failure. It seems that the classpath is not being searched, perhaps just the WAR classloader, not the JARs in WEB-INF/lib.

Next I tried omitting the / (i.e. using classloader:log4j2.xml) and got a NullPointerException.

Can you please document what schemes are supported and what you expect them to do, and not fail silently when a configuration file is specified, but nothing happens.

Issue Links

• is duplicated by: LOG4J2-357 log4jConfiguration via log4j.xml on classpath
• is related to: LOG4J2-357 log4jConfiguration via log4j.xml on classpath
• is related to: LOG4J2-359 Log4jServletContextListener does not work on Weblogic 12.1.1 (12c) with web-app version "2.5"
• is related to: LOG4J2-270 Improve logging initialization in Servlet containers; reduce amount of extra configuration needed in these contexts
• relates to: LOG4J2-394 ClassLoaderContextSelector logging WARN messages