DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39126>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39126 Summary: on some conditions, tomcat 'forget' an exception Product: Tomcat 5 Version: 5.5.7 Platform: All OS/Version: All Status: NEW Keywords: ErrorMessage Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Servlet specs tells the container must redirect to error page in case of exception inside jsp. It also allow webapp to provide it's own error handling jsp page. Sometimes, because response has already partially been send, tomcat is unable to send this redirect. This is somehow a behaviour the coder has to expect. However, when this happen, nowhere in tomcat is the original error logged. All you get is: 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.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) As a conclusion, all the programmer get as information is 'something bad occured during process of jsp, but i won't tell you where...' which is really useless information! Solution, What ever piece of code (errorvalve?) drop the above message in logs should also dump in logs the original jsp exception (you can't process the exception using an error page? then at least dump it in console) looks like trivial to implement. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
