https://issues.apache.org/bugzilla/show_bug.cgi?id=51859
Bug #: 51859
Summary: When JasperException occurs, error-pages are not
handled properly
Product: Tomcat 7
Version: 7.0.20
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: Jasper
AssignedTo: dev@tomcat.apache.org
ReportedBy: gl...@abv.bg
Classification: Unclassified
I'm using spring-mvc, and when it invokes requestDispatcher.forward(..), if a
JasperException occurs (for example "property active not found on type X"),
error-page handling is not taken into account. Here's the behavour:
- <error-page> entries in web.xml are not consulted - no matter if I map
java.lang.Exception, status 500, or status 330 (which is actually sent after
such an exception occurs)
- if I have a <%@ page errorPage="/500.jsp" %> then the exception is not logged
anywhere, but the error page is shown only if the page buffer is big enough to
reach the problematic part of the jsp. If the buffer is not big enough, a
partial page is shown, and no exception is logged.
The expected behaviour is to:
- forward to the error page regardless of the buffer size
- respect <error-page> entries in web.xml
- still log the exception (not sure about that).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
