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 2011/09/21 08:35:05 UTC

DO NOT REPLY [Bug 51859] New: When JasperException occurs, error-pages are not handled properly

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: glamd@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

DO NOT REPLY [Bug 51859] When JasperException occurs, error-pages are not handled properly

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=51859

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID
         OS/Version|                            |All

--- Comment #1 from Mark Thomas <ma...@apache.org> 2011-09-21 13:11:51 UTC ---
Forwards are not permitted once the response is committed.

Error pages do work although there are lots of things you can do within your
application that will prevent them from working - mainly committing the
response.

All unhandled exceptions are logged.


This looks like a series of usage issues rather than bugs and the Tomcat users
mailing list is the place to seek help.

-- 
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org