Christopher, You're right! It took me some time to get error.jsp coexist properly with the web service but there are no more Tomcat/Spring traces in error responses.
Thank you very much! On Tue, May 5, 2009 at 11:56 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > B.D, > > On 5/4/2009 4:23 PM, B D wrote: > > I run a Spring web service application under Tomcat 5.5.25 and need to > > eliminate stack traces from all error responses. > > > > For Tomcat 3.2 you could add showDebugInfo="false" to server.conf but > this > > is not an option for 5.5. > > > > Defining <error-page> in web.xml to handle all exceptions > > (<exception-type>java.lang.Throwable</exception-type>) does not help. I > am > > not sure if that's related to the fact that exception is thrown before > > request object is fully created and any of my code is actually called. > > The request is fully created by the time Spring gets called, so you > don't have to worry about anything weird like that. > > > From logs: > > SEVERE: Exception Processing ErrorPage[exceptionType=java.lang.Throwable, > > location=/error.jsp] > > I recommend fixing your error.jsp so that it doesn't throw its own > exception: it looks like error.jsp itself is broken, to TC is > falling-back on its own default error page. > > What do you get if you try to visit /error.jsp without an actual error > occurring? > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkoAYaEACgkQ9CaO5/Lv0PAn4gCfa3r/fis2hKG3MAizhUEJj1Du > S4wAn0WXmyIEdp+7FziGtYQoBQ8FWNys > =iW4J > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
