Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-18 Thread James Stauffer
With a lot of help from Ceki we finally got it to work. He helped me find that the issue was that commons logging wasn't finding log4j. Upgrading (from 1.0.2) to 1.0.4 fixed the problem! Version 1.0.2 apparently came with Tomcat 5.0.27. Thanks Ceki! -- James Stauffer http://www.geocities.com/

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-17 Thread James Stauffer
Ceki Gülcü <[EMAIL PROTECTED]> wrote: > The other (preferred) setting is: > CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar:"$CATALINA_HOME"/bin/commons-logging-api.jar:" > > ./bin/commons-logging-api.jar > ./common/lib/log4j.jar > ./common/lib/commons-logging.jar I changed to the prefe

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-17 Thread Ceki Gülcü
James, The fact that the setup you describe works is just happenstance. One setting I suggested was: CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/bootstrap.jar:"$CATALINA_HOME"/bin/commons-logging.jar:"$CATALINA_HOME"/bin/log4j.jar With NO copies of commons-logging.jar or log4j.jar in commons/lib. T

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-16 Thread James Stauffer
More info: I changed the Config servlet to write a few logs with logger.debug and logger.error and that info gets to the files but not anything besides that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-16 Thread James Stauffer
Could the problem be that I called LogLog.debug before configure? public class ConfigLog4jServlet extends HttpServlet { public void init() { String prefix = getServletContext().getRealPath("/"); String file = getInitParameter("log4j-init-file"); String fullPath = pref

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
Ceki Gülcü <[EMAIL PROTECTED]> wrote: > Place commons-logging.jar and log4j.jar on the CLASSPATH by modifying > catalina.sh. Make sure that no other copy of commons-logging.jar > or commons-logging-api.jar or log4j exists in your system visible to Tomcat. > > Try that and see what happens. CLAS

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread Ceki Gülcü
At 07:52 PM 2/15/2005, James Stauffer wrote: On Tue, 15 Feb 2005 19:47:56 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote: > > The most basic thing you could try is to place log4j What? Please ignore my comment above. > I'd place commons-logging.jar and log4j.jar on the CLASSPATH by modifying > catali

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
On Tue, 15 Feb 2005 19:47:56 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote: > > The most basic thing you could try is to place log4j What? > I'd place commons-logging.jar and log4j.jar on the CLASSPATH by modifying > catalina.sh and see what happens. Note that there must be no other copies > of com

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread Ceki Gülcü
The most basic thing you could try is to place log4j At 07:37 PM 2/15/2005, you wrote: If I add -Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.Log4jFactory That won't work because the commons-logging-api.jar placed on the system CLASSPATH (catalina.sh adds bin/commons-log

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
If I add -Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.Log4jFactory then catalina.out says the following. Do I need to add commons-logging.jar to the classpath? Bootstrap: Class loader creation threw exception java.lang.ExceptionInInitializerError at org.apache.

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
Ceki Gülcü <[EMAIL PROTECTED]> wrote: > What does TOMCAT_HOME/log/catalina.out say? Do you want me to send you the whole file? Should I send it to you directly? I also used the JSP at http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=499567 to check the config and it looks correct. --

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread Ceki Gülcü
At 06:50 PM 2/15/2005, you wrote: Ceki Gülcü <[EMAIL PROTECTED]> wrote: > Join the club of users been bitten by Jakarta Commons Logging and > its "smart" discovery process. > > You did not specify which minor version of Tomcat 5.0 it was. 5.0.27 > Anyway, if it is Tomcat 5.0.27 or later, then keep

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
Ceki Gülcü <[EMAIL PROTECTED]> wrote: > Join the club of users been bitten by Jakarta Commons Logging and > its "smart" discovery process. > > You did not specify which minor version of Tomcat 5.0 it was. 5.0.27 > Anyway, if it is Tomcat 5.0.27 or later, then keep the commons-logging and > log4j

Re: JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread James Stauffer
On Tue, 15 Feb 2005 18:19:52 +0100, Ceki Gülcü <[EMAIL PROTECTED]> wrote: > You did not specify which minor version of Tomcat 5.0 it was. Anyway, > if it is Tomcat 5.0.27 or later, then keep the commons-logging and > log4j jars in the following locations: 5.0.27. I'll give that a try. --

JCL+Tomcat+Log4j related problems [Was: Debugging]

2005-02-15 Thread Ceki Gülcü
James, Join the club of users been bitten by Jakarta Commons Logging and its "smart" discovery process. You did not specify which minor version of Tomcat 5.0 it was. Anyway, if it is Tomcat 5.0.27 or later, then keep the commons-logging and log4j jars in the following locations: TOMCAT_HOME/bin/com