Mmmm, for some reason it is using all the right class loaders to attempt to find the log4j.xml file, but it only uses 1 different methods to try to find log4j.properties. That is odd. Is this a Tomcat 4.1 specific class loader issue?
That's probably a cut-n-paste issue. Log4j searches for the log4j.xml file first, but otherwise it searches in the same way as for the log4j.properties file.
What about trying converting your log4j.properties file into a log4j.xml file, and placing it in the same spot. Given the catalina.out is attempting to look for that file in the right spots it should find it.
Using log4j.properties is fine. No need to convert to log4j.xml on account of initialization.
Paul
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
