https://issues.apache.org/bugzilla/show_bug.cgi?id=48795
Summary: Tomcat tries to use cache when compilation failed Product: Tomcat 6 Version: 6.0.24 Platform: PC OS/Version: Windows Vista Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: apa...@scribeofthenile.com Created an attachment (id=25037) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=25037) Full error log. After compilation of a JSP fails, Tomcat will often still try to use the (non-existant) cached version. For example, I have a simple JSP containing only "Hello, <%=name%>". When accessing for the first time, Tomcat throws "org.apache.jasper.JasperException: Unable to compile class for JSP". Subsequent requests will alternate between this error, and "java.lang.ClassNotFoundException: org.apache.jsp.jsp.test_jsp". In the case of editing existing JSPs which have compiled fine, the response will alternate between the original error, and the cache of the last-good JSP. I'm using Sun JVM 1.6.0_18-b07. -- 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org