Jetty
  1. Jetty
  2. JETTY-1327

Duplicate local variable _jspx_temp0

    Details

    • Type: Bug Bug
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 7.1.6
    • Fix Version/s: None
    • Component/s: JSP
    • Labels:
      None
    • Environment:
      CentOS 5, Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing)
    • Number of attachments :
      0

      Description

      Noticed the following error in server's logs:
      org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP

      PWC6197: An error occurred at line: 4 in the jsp file: <name here>.jsp
      PWC6199: Generated servlet error:
      Duplicate local variable _jspx_temp0

      This seems to be a Jasper error already reported and fixed a long time ago in Tomcat: https://issues.apache.org/bugzilla/show_bug.cgi?id=45691

      The above link also contains a full war to replicate.

      Other people reported the same problem under Jetty 6.1.19: http://youtrack.jetbrains.net/issue/TW-10511?query=by
      From the solution reported in jetbrains forums (clean work folder, restart), this clearly is a random issue occurring only on particular concurrent compilation scenarios.

      Is Jasper included in the current Jetty patched the same way as reported in the fix for Tomcat 6.0.19? It seems that Jetty uses Jasper from Glassfish, I wonder if that patch made it through...

        Activity

        Hide
        Dan Ruthers added a comment -

        jboss only incorporated this fix in July 2010:
        https://issues.jboss.org/browse/JBPAPP-4547

        Show
        Dan Ruthers added a comment - jboss only incorporated this fix in July 2010: https://issues.jboss.org/browse/JBPAPP-4547
        Hide
        Greg Wilkins added a comment -

        We are considering switching back to use the tomcat jasper rather than the glassfish one.
        stay tuned

        Show
        Greg Wilkins added a comment - We are considering switching back to use the tomcat jasper rather than the glassfish one. stay tuned
        Hide
        Jan Bartel added a comment -

        Dan,

        It doesn't look to me as if this is fixed in the glassfish codebase for jsp-2.1 nor jsp-2.2. At least, this particular patch seems not be applied. I can't see any changes that might be related to it either. Can I suggest you raise this as an issue at the glassfish jsp project to be fixed? The link is here: http://jsp.java.net/

        thanks
        Jan

        Show
        Jan Bartel added a comment - Dan, It doesn't look to me as if this is fixed in the glassfish codebase for jsp-2.1 nor jsp-2.2. At least, this particular patch seems not be applied. I can't see any changes that might be related to it either. Can I suggest you raise this as an issue at the glassfish jsp project to be fixed? The link is here: http://jsp.java.net/ thanks Jan
        Hide
        Dan Ruthers added a comment -

        Jan, thanks.
        I've now opened a ticket at http://java.net/jira/browse/JSP-20 , let's see what happens...

        Show
        Dan Ruthers added a comment - Jan, thanks. I've now opened a ticket at http://java.net/jira/browse/JSP-20 , let's see what happens...
        Hide
        Jan Bartel added a comment -

        Info: this bug still exists in jsp-impl-2.2.2.b05.

        Show
        Jan Bartel added a comment - Info: this bug still exists in jsp-impl-2.2.2.b05.

          People

          • Assignee:
            Jan Bartel
            Reporter:
            Dan Ruthers
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: