You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/11/04 17:36:35 UTC
DO NOT REPLY [Bug 14230] New: -
JSP errorPage mechanism is failing in HEAD build of Tomcat 5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14230
JSP errorPage mechanism is failing in HEAD build of Tomcat 5
Summary: JSP errorPage mechanism is failing in HEAD build of
Tomcat 5
Product: Tomcat 5
Version: Nightly Build
Platform: All
OS/Version: All
Status: NEW
Severity: Blocker
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: Ryan.Lubke@Sun.COM
It would seem a problem has appeared in dispatching a request to an error page
defined in a JSP.
Here is an example of the failure from Watchdog:
[java] [watchdog] ERROR: Server's response and configured goldenfile do not
match!
[java] [watchdog] Response received from server:
[java] [watchdog] ---------------------------------------------------------
[java] [watchdog] <html><head><title>Apache Tomcat/5.0 - Error
report</title><STYLE><!--H1{font-family : sans-serif,Arial,Tahoma;color :
white;background-color : #0086b2;} H3{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color :
white;} B{color : white;background-color : #0086b2;} HR{color : #0086b2;}
--></STYLE> </head><body><h1>HTTP Status 500 - </h1><HR size="1"
noshade><p><b>type</b> Exception report</p><p><b>message</b>
<u></u></p><p><b>description</b> <u>The server encountered an internal error ()
that prevented it from fulfilling this request.</u></p><p><b>exception</b>
<pre>java.lang.ArithmeticException: / by zero
[java] [watchdog] at
org.apache.jsp.positiveErrorPage_jsp._jspService(positiveErrorPage_jsp.java:63)
[java] [watchdog] at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:135)
Instead of the defined error page being invoked, the default error page
mechanism for uncaught exceptions is being used.
I don't believe this to be an issue with Jasper2 as it relies on the Servlet
container's RequestDispatcher to handle this functionality.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>