Howdy, The simplest way: look into server.xml, change all debug="0" to debug="99". This will get more info than you probably want, but that's (usually) a good thing when debugging ;)
As an aside: classpath problems typically don't require that much debugging information. If you get a class not found type of error, make sure the class or a jar containing it is visible to your web application. See the tomcat 4.x classloader documentation at: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/class-loader-howto.html I hope this helps, Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: David Goodenough [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, July 09, 2002 6:37 AM >To: [EMAIL PROTECTED] >Subject: Classpath problems > >I am having the inevitable initial classpath problems setting up my first >servlet under Tomcat 4.0.3 (the one shipped with Sun JWSDP). In the source >code I see there are debug levels and some increased debug levels, but >I am unsure about how I am supposed to enable them. I tried setting >an init-param of debug to 9 in my web.xml, but no luck. > >Thanks in advance > >David > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
