beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Updated: (BEEHIVE-757) 503 error when @Jpf.Catch forwards to an error page with a compile error in it
Date Wed, 22 Jun 2005 19:50:23 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-757?page=all ]

Rich Feit updated BEEHIVE-757:
------------------------------

    Fix Version: V1
                     (was: TBD)
    Description: 
Repro:
    - Add the attached page flow to a Beehive webapp, build, and hit /foo/Controller.jpf.

    - Click the 'throwException' link.

EXPECTED: a Tomcat error page for the IllegalStateException thrown from the page.
ACTUAL: a 503 error returned to the browser; the original exception is nowhere to be found,
in the logs or on the console.

This only happens when the JSP's page flow has a @Jpf.Catch with type=Exception.class.  There's
an infinite loop happening, where the page exception is getting caught by the @Jpf.Catch,
which re-forwards to the error page.  The 503 is the Page Flow framework's decision to break
out of the string of forwards when some threshold is reached (25 by default).

  was:
Repro:
    - Add the attached page flow to a Beehive webapp, build, and hit /foo/Controller.jpf.

    - Click the 'throwException' link.

EXPECTED: a Tomcat error page describing the compilation error on the page ('blah' is not
a valid attribute for netui:anchor).
ACTUAL: a 503 error returned to the browser; the original exception is nowhere to be found,
in the logs or on the console.

This only happens when the JSP's page flow has a @Jpf.Catch with type=Exception.class.  There's
an infinite loop happening, where the Jasper exception is getting caught by the @Jpf.Catch,
which re-forwards to the error page.  The 503 is the Page Flow framework's decision to break
out of the string of forwards when some threshold is reached (25 by default).


I never attached the repro -- will do it shortly.

> 503 error when @Jpf.Catch forwards to an error page with a compile error in it
> ------------------------------------------------------------------------------
>
>          Key: BEEHIVE-757
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-757
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: v1m1
>  Environment: Tomcat 5.0.25
>     Reporter: Rich Feit
>     Assignee: Rich Feit
>      Fix For: V1

>
> Repro:
>     - Add the attached page flow to a Beehive webapp, build, and hit /foo/Controller.jpf.
>     - Click the 'throwException' link.
> EXPECTED: a Tomcat error page for the IllegalStateException thrown from the page.
> ACTUAL: a 503 error returned to the browser; the original exception is nowhere to be
found, in the logs or on the console.
> This only happens when the JSP's page flow has a @Jpf.Catch with type=Exception.class.
 There's an infinite loop happening, where the page exception is getting caught by the @Jpf.Catch,
which re-forwards to the error page.  The 503 is the Page Flow framework's decision to break
out of the string of forwards when some threshold is reached (25 by default).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message