Re: standard valve / errors handling
Bill Barker a écrit : Problem: because of the valve problem, my jsp is not called. This jsp is supposed to handle displaying of this NullPointerException's stacktrace(). Is there a way to configure the standard valve so that is dumps the stacktrace in tomcat log? Well, it isn't really the valve's problem, so much as it a problem with the webdav servlet :). Tomcat has already send the Response headers back to the browser (and probably part of the Response body as well), so there is no way (under the HTTP protocol) for it to tell the browser oops, this is what I meant to send. I know that, an my question is still Is there a way to configure the standard valve so that is dumps the stacktrace in tomcat log? My problem is to get access to that NullPointerException so i can fix the servlet :) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
standard valve / errors handling
Hello, it is my understanding that tomcat uses a valve to detect Throwables from webapp and redirect to error page. However, in some case, it seems impossible to redirect to error page: 68937425 [http-8081-Processor14] ERROR StandardWrapper[/intranet:webdav] - Servlet.service() for servlet webdav threw exception java.lang.NullPointerException Aug 17, 2007 9:11:36 AM org.apache.catalina.core.StandardHostValve custom SEVERE: Exception Processing ErrorPage[exceptionType=java.lang.Exception, location=/jsp/error.jsp] java.lang.IllegalStateException at org.apache.coyote.Response.reset(Response.java:296) at org.apache.catalina.connector.Response.reset(Response.java:642) at org.apache.catalina.connector.Response.reset(Response.java:908) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:355) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:211) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:534) Problem: because of the valve problem, my jsp is not called. This jsp is supposed to handle displaying of this NullPointerException's stacktrace(). Is there a way to configure the standard valve so that is dumps the stacktrace in tomcat log? Thank you. -- http://www.noooxml.org/ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: standard valve / errors handling
David Delbecq [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, it is my understanding that tomcat uses a valve to detect Throwables from webapp and redirect to error page. However, in some case, it seems impossible to redirect to error page: 68937425 [http-8081-Processor14] ERROR StandardWrapper[/intranet:webdav] - Servlet.service() for servlet webdav threw exception java.lang.NullPointerException Aug 17, 2007 9:11:36 AM org.apache.catalina.core.StandardHostValve custom SEVERE: Exception Processing ErrorPage[exceptionType=java.lang.Exception, location=/jsp/error.jsp] java.lang.IllegalStateException at org.apache.coyote.Response.reset(Response.java:296) at org.apache.catalina.connector.Response.reset(Response.java:642) at org.apache.catalina.connector.Response.reset(Response.java:908) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:355) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:211) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:134) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:534) Problem: because of the valve problem, my jsp is not called. This jsp is supposed to handle displaying of this NullPointerException's stacktrace(). Is there a way to configure the standard valve so that is dumps the stacktrace in tomcat log? Well, it isn't really the valve's problem, so much as it a problem with the webdav servlet :). Tomcat has already send the Response headers back to the browser (and probably part of the Response body as well), so there is no way (under the HTTP protocol) for it to tell the browser oops, this is what I meant to send. Thank you. -- http://www.noooxml.org/ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
