Hi all, Recently I've ported our 5.0.28 server to 5.5.9 and JSVC. In the process I spent some time converting the server logging over to use log4j, which I've used on my webapps successfully for a while now.
I've consulted the FAQ articles, which were very useful (except the last one: Need for it to be in bootstrap classpath. This link appears to be broken?). I've implemented the solution posted in 'Example with JSVC and running on port 80.' and am now sucessfuly logging tomcat server messages correctly to where I want them (catalina.log in $CATALINA_HOME/logs). The issue that I'm having now is that everything, including my webapps, now logs to this file, eschewing their own logging setups (including commons-loggin and log4j in WEB-INF/lib and log4j.xml in WEB-INF/classes). My best guess is the classloading situation as described at http://jakarta.apache.org/tomcat/tomcat-5.5-doc/class-loader-howto.html, that says in the eyes of my web app, classes are loaded in this order: Bootstrap classes of your JVM System class loader classses (described above) /WEB-INF/classes of your web application /WEB-INF/lib/*.jar of your web application $CATALINA_HOME/common/classes $CATALINA_HOME/common/endorsed/*.jar $CATALINA_HOME/common/i18n/*.jar $CATALINA_HOME/common/lib/*.jar $CATALINA_BASE/shared/classes $CATALINA_BASE/shared/lib/*.jar Since I've added log4j.xml (specifically, $CATALINA_HOME/common/classes where it resides, as described in the FAQ) to the bootstrap classpath, it's seeing the global log4j before it sees the app's. Do this sound right? If so, how do I get around this behavior so my wbapps will log using individual setups? Forgive me if this has been covered. I scanned as best I could for references in the archive. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
