I WISH we could upgrade to tomcat 5, but that's something penned for
the future. Good news is I have got a solution to the problem.
By using log4j's default initialisation procedure of putting
log4j.properties in the classpath, everything is working as needed now.
Upon recompile, the log4j set
Is there a particular reason you are still using 3.2? If you upgrade to
5.x.xx, I can give you more advice. 3.2 was a *very* different product and
few people use it anymore. I'm not surprised you've had little luck in
finding help with a product 4 years out of date. You might find more help
Hi all,
I'm using log4j 1.2.8 in a webapp deployed under Tomcat 3.2.
In the development environment, reloadable=true for the webapp's
context, so I can compile java changes into the webapp without stopping
and starting tomcat.
After starting the webapp up, all the logging is directed to the
vari
