RE: WebappClassLoader: Lifecycle error : CL stopped

2004-03-18 Thread Shapira, Yoav
-Original Message- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004 12:31 AM To: Tomcat Users List Subject: Re: WebappClassLoader: Lifecycle error : CL stopped At 10:38 PM 3/17/2004 +, you wrote: Hi, Thank you for that, and excuse my delay in responding. I

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-18 Thread Jerald Powel
Hello, Yes, I see it in the Javadoc. Here's my confusion. I am not 'using' Log4j-1.2.8 at all! To implement the logic you talk of, I would have to get a JAR from the Apache web site? Even though I am not using Log4j whatsoever on my app, is this necessary? I dont know what class I was

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-18 Thread Jerald Powel
I have put down to the method not found thing to I my importing java.util.logging.LogManager! I have since acquired the JAR from Apache.org, implemented: public void contextDestroyed(ServletContextEvent event) { org.apache.log4j.LogManager.shutdown(); } in a servlet

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-18 Thread Jacob Kjome
Quoting Jerald Powel [EMAIL PROTECTED]: Hello, Yes, I see it in the Javadoc. Here's my confusion. I am not 'using' Log4j-1.2.8 at all! To implement the logic you talk of, I would have to get a JAR from the Apache web site? Yes, but you are using commons-logging and

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-18 Thread Jacob Kjome
See my other message for the reasoning. I would recommend not to use commons-logging in your code. It does nothing for you and can only cause problems. Just use Log4j directly. If other apps use commons-logging such as Struts, you'll obviously have to include commons-logging, but don't let it

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-17 Thread Jerald Powel
Hi, Thank you for that, and excuse my delay in responding. I tried what you suggested, but found the LogManager class did not contain such a method. It did have one method to speak of - getLogManager() which returns an instance of LogManager, but that also has no shutdown method. I found

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-17 Thread Jacob Kjome
At 10:38 PM 3/17/2004 +, you wrote: Hi, Thank you for that, and excuse my delay in responding. I tried what you suggested, but found the LogManager class did not contain such a method. It did have one method to speak of - getLogManager() which returns an instance of LogManager, but

WebappClassLoader: Lifecycle error : CL stopped

2004-03-15 Thread Jerald Powel
Hello all, Can anyone shed some light on the above error please? On the web, I saw it often associated with NoClassDefFoundError, and something called DOMConfigurator. May app does indeed parse XML (JDom and Nano XML). Is this message linked to an error possibly residing in my XML

Re: WebappClassLoader: Lifecycle error : CL stopped

2004-03-15 Thread Jacob Kjome
This has to do with Log4j. Make sure you set up a servlet context listener and do LogManager.shutdown() in the contextDestroyed() method. This will take care of your troubles. Jake At 02:13 AM 3/16/2004 +, you wrote: Hello all, Can anyone shed some light on the above error

WebappClassLoader: Lifecycle error : CL stopped

2002-01-24 Thread Tim Veazey
/se/... blah... blah... WebappClassLoader: Lifecycle error : CL stopped Subsequently, I don't have access to any of my web-app library classes. Below is my server.xml config for this webapp. Anyone know what the problem might be? Thanks in advance. Context path=/reparts docBase=reparts debug=0