root cause java.util.NoSuchElementException java.util.ArrayList$Itr.next(ArrayList.java:834) org.apache.jasper.compiler.Validator$ValidateVisitor.getJspAttribute(Validator.java:1385) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:772) org.apache.jasper.compiler.Node$UninterpretedTag.accept(Node.java:1251) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2429) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:779) org.apache.jasper.compiler.Node$UninterpretedTag.accept(Node.java:1251) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2429) org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:529) org.apache.jasper.compiler.Node$JspRoot.accept(Node.java:564) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2429) org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2435) org.apache.jasper.compiler.Node$Root.accept(Node.java:474) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2377) org.apache.jasper.compiler.Validator.validateExDirectives(Validator.java:1841) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:217) org.apache.jasper.compiler.Compiler.compile(Compiler.java:373) org.apache.jasper.compiler.Compiler.compile(Compiler.java:353) org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:657) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) ... It fails on e.g. on the following line: <body ui-view=""></body> These changes happened in bug 56334.
Thanks for the report. This has been fixed in trunk for 8.0.9 and in 7.0.x for 7.0.55 onwards. The fix is proposed for Tomcat 6.
Thanks for applying a fix. Would it make sense to revoke the recent releases and make a new ones with the fix soon?
We don't revoke releases, we just produce a new release. How quickly the next set of releases happens depends on a number of factors. I was planning another 8.0.x shortly anyway to try and get back to a monthly release cycle. I can also do 6.0.x if necessary. It is always a balancing act between waiting to see if further issues emerge and getting another release out. At this point, I think it probably makes sense to wait a little longer. I'll aim to do a new 6.0.x release shortly after the next 8.0.x release.
I also plan another 7.0.x release at the beginning of the next month.
This has been fixed in 6.0.x for 6.0.42 onwards.
*** Bug 56610 has been marked as a duplicate of this bug. ***