Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 80297 invoked from network); 19 Apr 2005 07:09:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Apr 2005 07:09:39 -0000 Received: (qmail 73196 invoked by uid 500); 19 Apr 2005 07:09:08 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 73149 invoked by uid 500); 19 Apr 2005 07:09:07 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 73097 invoked by uid 99); 19 Apr 2005 07:09:06 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 19 Apr 2005 00:09:05 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 33B3B2DD; Tue, 19 Apr 2005 09:09:01 +0200 (CEST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 34513] New: - jsp exception handling X-Bugzilla-Reason: AssignedTo Message-Id: <20050419070901.33B3B2DD@ajax.apache.org> Date: Tue, 19 Apr 2005 09:09:01 +0200 (CEST) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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=34513 Summary: jsp exception handling Product: Tomcat 5 Version: 5.0.28 Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: shengshen@gmail.com I use the following directive <%@ page errorPage="/jsp/error.jsp" %> to tell jsp to move to error.jsp when exception raises on the page. But I noticed the the real behavior relates to the "position" that the exception raises on the JSP page: 1.When it raises on the relatively front part of the page, the page is redirected correctly to /jsp/error.jsp 2.if exception raises at relatively rear position, the contenct of the /jsp/error.jsp is outputed right after the normal output of the page. 3.If at even rearer position, the result is a weird "chopped" page with only part of normal output. I tried to debugged the src of jasper into PageContextImpl's doHandlePageException method. Found that the situation 2 was caused by "JspWriterImpl has already flushed", the situation 3 was caused by the "response was already committed". I can't understand this behavior of tomcat. Isn't it puzzling to the ones that want to debug JSP page? -- 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: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org