My servlet application includes a number of library .jars, some of which contain embedded log4j.xml or log4j.properties files. I’d like to ensure that log4j finds my log4j.xml first! I’ve tried searching for some specification of the priorities of the various classpath elements in a servlet (e.g. does WEB-INF/classes always precede WEB-INF/lib?), or some way to configure or tweak the servlet’s classloader so that a given resource directory appears early in the classpath. So far, I’ve drawn a blank. Any suggestions on ensuring that a servlet .war file loads the correct log4j.xml via the classloader?
My servlet application includes a number of library .jars, some of which contain embedded
Share
As far as I understand the resource selection from the classpath is non-deterministic (from the point of view of the app developer). Even if the same file is loaded consistently the behaviour could change: 1. When you upgrade the version of your current container. 2. If you switch containers.
The simplest solution will be to remove embedded log4j config files from library jars. It is almost never a good idea to embed log4j config’s as it leads to the problem you are seeing here…
Are they third party jars or jars you developed?