Why Tomcat uses ROOT context's log4j and log4j.properties?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Why Tomcat uses ROOT context's log4j and log4j.properties?

Son KwonNam
Hello,
I have a problem that Tomcat uses ROOT web application context's
log4j-1.2.8.jar and log4j.properties.

I installed Tomcat 5.0.28, Java 1.4.2_09 and deployed root context web
application to $CATALINA_HOME/webapps/ROOT on Solaris 8.
I DO NOT change anything in $CATALIN_HOME/conf/server.xml.

And there are the following files

$CATALINA_HOME/webapps/ROOT/WEB-INF/lib/commons-logging.jar
$CATALINA_HOME/webapps/ROOT/WEB-INF/lib/log4j-1.2.8.jar
$CATALINA_HOME/webapps/ROOT/WEB-INF/classes/log4j.properties


$CATALINA_HOME/servers or common, share directory don't have any log4j
related files.

also system classpath variable does not include
$CATALINA_HOME/webapps/ROOT/WEB-INF/lib/*.jar or
$CATALINA_HOME/webapps/ROOT/WEB-INF/classes directory.
I also checked $JAVA_HOME/jre/lib/ext, there is nothing related to log4j.

But Tomcat uses log4j and log4j.properties settings for it's logging(of
course also for ROOT WebApp context's logging) not commons-logging's simple
logger.

What should I do for the tomcat not to use web context's log4j??

Also, I can see catalian.out, but actually after using Tomcat 5.0.28 on
other machine, I've never seen the file.

Regards,
KwonNam.