Thanks for the link. I've read that before, but forgot about it. I've checked both of my WEB-INF/lib directories and each has all the lib's. I might resort to hardcoding the paths in since that seemed to work, but I hate doing that.
Does Tomcat 5.x have the same issues? How about jetty or resin? ---------- Forwarded Message ---------- Subject: Re: Turbine 2.3 loggin problem. Date: Wednesday 18 August 2004 01:55 am From: Babu Kalakrishnan <[EMAIL PROTECTED]> To: Turbine Users List <[EMAIL PROTECTED]> Marty Phee wrote: >I have the Log4j file in the conf directory. I tried to move it to the >classes folder, but log4j would complain that it couldn't find the file in >the conf directory even after I commented out the line in the turbine conf >for Log4j. It could perhaps be a Classloader issue. Check if the jar files for commons-logging and log4j are available in the WEB-INF/lib directory of *both* applications - so that both applications are working with their own copies of the Logging system loaded with different classloaders. Sharing a classloader (which can happen if either of the jars come from the common directory of Tomcat) can cause all sorts of confusion in logging. This article (and the links referred to in the article) makes interesting reading : http://www.qos.ch/logging/thinkAgain.html BK --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
