RE: Problem with logging in Eclipse
For what it's worth my logs show: - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Logger at... rather than the - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout at. noted below. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 11:22 AM To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Donie, I just noticed this from your log: - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout I'm at work right now so can't check my logs at home but if they also point to Layout as the missing class rather than just Log4j that may tell us a little more about what's causing the problem. I didn't think that my errors pointed to Layout but I could be wrong. Ken -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 5:19 AM To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Anybody else have this problem??? Thanks Donie -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: 28 October 2004 11:12 To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Hi guys I have the same problem and it's driving me nuts. I have a run configuration in Eclipse 3.0 for tomcat 4.1.18 and I call bootstrap.jar directly within eclipse to start tomcat. The only jars I put in the run configuration class path are the tomcat ones. This starts tomcat as it would be normally run and tomcat then inits the webapps directory and creates the classpath for each webapp based on the contents of the WEB-INF/lib. I have commons-logging.jar in my WEB-INF/lib as it's required by some code. This has problems finding log4j even though it's there. When I send in a request that uses com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory tomcat throws an exception into Catalina.out log showing the following stack trace below. Now, if I put log4j.jar into the run configuration class path the problem goes away? Why can't tomcat find this jar under Eclipse 3 However, because I have multiple webapps running, the logging for the different webapps is the same as the log4j.jar is now global so the last webapp to init sets the logging scheme and location. Painful. Thanks Donie 2004-10-28 11:14:41 StandardWrapperValve[webclient]: Servlet.service() for servlet webclient threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline
RE: Problem with logging in Eclipse
And, mine shows Catalog. From: Januski, Ken [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: RE: Problem with logging in Eclipse Date: Mon, 1 Nov 2004 11:32:12 -0500 For what it's worth my logs show: - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Logger at... rather than the - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout at. noted below. -Original Message- From: Januski, Ken [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 11:22 AM To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Donie, I just noticed this from your log: - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout I'm at work right now so can't check my logs at home but if they also point to Layout as the missing class rather than just Log4j that may tell us a little more about what's causing the problem. I didn't think that my errors pointed to Layout but I could be wrong. Ken -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 5:19 AM To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Anybody else have this problem??? Thanks Donie -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: 28 October 2004 11:12 To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Hi guys I have the same problem and it's driving me nuts. I have a run configuration in Eclipse 3.0 for tomcat 4.1.18 and I call bootstrap.jar directly within eclipse to start tomcat. The only jars I put in the run configuration class path are the tomcat ones. This starts tomcat as it would be normally run and tomcat then inits the webapps directory and creates the classpath for each webapp based on the contents of the WEB-INF/lib. I have commons-logging.jar in my WEB-INF/lib as it's required by some code. This has problems finding log4j even though it's there. When I send in a request that uses com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory tomcat throws an exception into Catalina.out log showing the following stack trace below. Now, if I put log4j.jar into the run configuration class path the problem goes away? Why can't tomcat find this jar under Eclipse 3 However, because I have multiple webapps running, the logging for the different webapps is the same as the log4j.jar is now global so the last webapp to init sets the logging scheme and location. Painful. Thanks Donie 2004-10-28 11:14:41 StandardWrapperValve[webclient]: Servlet.service() for servlet webclient threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480
RE: Problem with logging in Eclipse
Anybody else have this problem??? Thanks Donie -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: 28 October 2004 11:12 To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Hi guys I have the same problem and it's driving me nuts. I have a run configuration in Eclipse 3.0 for tomcat 4.1.18 and I call bootstrap.jar directly within eclipse to start tomcat. The only jars I put in the run configuration class path are the tomcat ones. This starts tomcat as it would be normally run and tomcat then inits the webapps directory and creates the classpath for each webapp based on the contents of the WEB-INF/lib. I have commons-logging.jar in my WEB-INF/lib as it's required by some code. This has problems finding log4j even though it's there. When I send in a request that uses com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory tomcat throws an exception into Catalina.out log showing the following stack trace below. Now, if I put log4j.jar into the run configuration class path the problem goes away? Why can't tomcat find this jar under Eclipse 3 However, because I have multiple webapps running, the logging for the different webapps is the same as the log4j.jar is now global so the last webapp to init sets the logging scheme and location. Painful. Thanks Donie 2004-10-28 11:14:41 StandardWrapperValve[webclient]: Servlet.service() for servlet webclient threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: 1040) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151 ) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout at org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:1 40) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja va:257) at com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory.clinit(ElementFactory .java:84) at com.sun.xml.messaging.saaj.soap.dom4j.EnvelopeFactoryImpl.createEnvelope(Env elopeFactoryImpl.java:67) at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:8 7
RE: Problem with logging in Eclipse
Donie, I just noticed this from your log: - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout I'm at work right now so can't check my logs at home but if they also point to Layout as the missing class rather than just Log4j that may tell us a little more about what's causing the problem. I didn't think that my errors pointed to Layout but I could be wrong. Ken -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: Friday, October 29, 2004 5:19 AM To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Anybody else have this problem??? Thanks Donie -Original Message- From: Donie Kelly [mailto:[EMAIL PROTECTED] Sent: 28 October 2004 11:12 To: Tomcat Users List Subject: RE: Problem with logging in Eclipse Hi guys I have the same problem and it's driving me nuts. I have a run configuration in Eclipse 3.0 for tomcat 4.1.18 and I call bootstrap.jar directly within eclipse to start tomcat. The only jars I put in the run configuration class path are the tomcat ones. This starts tomcat as it would be normally run and tomcat then inits the webapps directory and creates the classpath for each webapp based on the contents of the WEB-INF/lib. I have commons-logging.jar in my WEB-INF/lib as it's required by some code. This has problems finding log4j even though it's there. When I send in a request that uses com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory tomcat throws an exception into Catalina.out log showing the following stack trace below. Now, if I put log4j.jar into the run configuration class path the problem goes away? Why can't tomcat find this jar under Eclipse 3 However, because I have multiple webapps running, the logging for the different webapps is the same as the log4j.jar is now global so the last webapp to init sets the logging scheme and location. Painful. Thanks Donie 2004-10-28 11:14:41 StandardWrapperValve[webclient]: Servlet.service() for servlet webclient threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: 1040) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151 ) at java.lang.Thread.run(Thread.java
RE: Problem with logging in Eclipse
Hi guys I have the same problem and it's driving me nuts. I have a run configuration in Eclipse 3.0 for tomcat 4.1.18 and I call bootstrap.jar directly within eclipse to start tomcat. The only jars I put in the run configuration class path are the tomcat ones. This starts tomcat as it would be normally run and tomcat then inits the webapps directory and creates the classpath for each webapp based on the contents of the WEB-INF/lib. I have commons-logging.jar in my WEB-INF/lib as it's required by some code. This has problems finding log4j even though it's there. When I send in a request that uses com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory tomcat throws an exception into Catalina.out log showing the following stack trace below. Now, if I put log4j.jar into the run configuration class path the problem goes away? Why can't tomcat find this jar under Eclipse 3 However, because I have multiple webapps running, the logging for the different webapps is the same as the log4j.jar is now global so the last webapp to init sets the logging scheme and location. Painful. Thanks Donie 2004-10-28 11:14:41 StandardWrapperValve[webclient]: Servlet.service() for servlet webclient threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:493) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: 1040) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151 ) at java.lang.Thread.run(Thread.java:534) - Root Cause - java.lang.NoClassDefFoundError: org/apache/log4j/Layout at org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:1 40) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja va:257) at com.sun.xml.messaging.saaj.soap.dom4j.ElementFactory.clinit(ElementFactory .java:84) at com.sun.xml.messaging.saaj.soap.dom4j.EnvelopeFactoryImpl.createEnvelope(Env elopeFactoryImpl.java:67) at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:8 7) at com.tecnomen.mms.client.eai.SOAPEncoder.decode(SOAPEncoder.java:256) at com.tecnomen.mms.client.eai.MessageFactory.createMIMEMessage(MessageFactory. java:340) at
Re: Problem with logging in Eclipse
I use eclipse 2.1.3, have you gone to Windows - Preferences and clicked on Tomcat ?? I don't know what Eclipse 3 looks like there, but in 2.1.3 i selected a project to use for my tomcat classpath. Additionally if you right-click your project - Properties click tomcat and in 2.1.3 you can say this is a Tomcat project order may be important here ;) e.g. i gave reverse order i think. Dave Been
RE: Problem with logging in Eclipse
This isn't much help but I have had a somewhat similar experience. I took the war for a working application running on Tomcat 4.0 at work and tried to get it running with Tomcat 5.0 and Eclipse 3.0 at home. It constantly complained about not being able to find log4j, this no matter where I put the log4j jar. Since this isn't something critical to me I haven't focussed on solving it, but have been playing with it intermittently for at least 2 months. But it does seem odd to me that Tomcat in Eclipse can never find it. You wouldn't think that log4j had to go in some special place in Eclipse. I hope someone else can shed some light. -Original Message- From: Glenn Barnard [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 11:11 AM To: [EMAIL PROTECTED] Subject: Problem with logging in Eclipse Hi, I'm new to this list so if my question has been answered previously, please give me a URL to look at---I have tried one without a hit. I am trying to use Tomcat 5.5 in my Eclipse 3.0 development environment. I have a Tomcat plugin which starts Tomcat from a simple icon. In following the limited instructions I've been able to find for installing log4j for Tomcat 5.5, I put commons-logging.jar and log4j.jar in the common/lib directory. As soon as I do that, Tomcat fails during startup with the following stack trace. The messages indicate that Catalog.class is not in the jar files, but I've confirmed that it is in log4j.jar in the correct package. I have brought in the source code, and tried to step through it, but I'm not getting anywhere with that. This AM I tried Tomcat 5.0 and got the same problem. Am not seeing any problem starting Tomcat directly from a DOS prompt. If anyone can help me, I'd surely appreciate it! Let me know if you have any questions about how I configure Tomcat, although I've tried server.xml without editing it. java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:208) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:402) Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@958bb8 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@958bb8 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category)) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja va:543) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja va:235) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja va:209) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351) at org.apache.catalina.core.StandardService.clinit(StandardService.java:53) ... 8 more Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@958bb8 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Category) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI mpl.java:413) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja va:529) ... 12 more Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Category at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.getConstructor(Unknown Source) at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI mpl.java:410) ... 13 more _ Express yourself instantly with MSN Messenger! Download today - it's FREE! hthttp://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with logging in Eclipse
Dave, Thanks for your response. My problem is not getting Eclipse to start Tomcat, it's getting Tomcat to run with logging, specifically log4j. It's failing on the second call to the logging function. From: Dave Been [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: Problem with logging in Eclipse Date: Wed, 27 Oct 2004 09:11:40 -0700 I use eclipse 2.1.3, have you gone to Windows - Preferences and clicked on Tomcat ?? I don't know what Eclipse 3 looks like there, but in 2.1.3 i selected a project to use for my tomcat classpath. Additionally if you right-click your project - Properties click tomcat and in 2.1.3 you can say this is a Tomcat project order may be important here ;) e.g. i gave reverse order i think. Dave Been _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
