Beehive
  1. Beehive
  2. BEEHIVE-757

503 error when @Jpf.Catch forwards to an error page with a compile error in it

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v1m1
    • Fix Version/s: 1.0
    • Component/s: NetUI
    • Labels:
      None
    • Environment:
      Tomcat 5.0.25

      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).

      1. j757.zip
        1 kB
        Rich Feit

        Activity

        Alejandro Ramirez made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Rich Feit made changes -
        Resolution Fixed [ 1 ]
        Assignee Rich Feit [ rich ] Alejandro Ramirez [ alramire ]
        Status Open [ 1 ] Resolved [ 5 ]
        Rich Feit made changes -
        Attachment j757.zip [ 12310905 ]
        Rich Feit made changes -
        Field Original Value New Value
        Fix Version/s TBD [ 10950 ]
        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 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).
        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).
        Fix Version/s V1 [ 12310123 ]
        Rich Feit created issue -

          People

          • Assignee:
            Alejandro Ramirez
            Reporter:
            Rich Feit
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development