Hi,
I'm not sure if there is anything that can be done about this, but I just
tried switching from Tomcat's standard JULI logging to Log4j implementation
following the docs at http://tomcat.apache.org/tomcat-6.0-doc/logging.html.
Overall, everything works as expected, although I found one signficiant
discrepancy between the two systems.
In JULI, the logging.properties file can be place in
${catalina.base}/conf/logging.properties, whereas Log4j expects it in
${catalina.home}/lib/log4j.properties. I am assuming that it is log4j which
is searching for it as part of the class path.
Although this may not seem overly significant, it does become quite so if
you have multiple tomcat installations with a single tomcat binary install.
Whereas with JULI, you can define individual logging based on the base
directory, with log4j, it would apply to every installation.
Is there a workaround for this, or just one of those things that you have to
learn to live with?
Thanks,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
