Why does Tomcat try to use the cache when compilation failed?
Posted
by etheros
on Server Fault
See other posts from Server Fault
or by etheros
Published on 2010-02-16T17:33:56Z
Indexed on
2010/03/22
18:01 UTC
Read the original article
Hit count: 326
For some reason, it appears Tomcat is trying to hit its compilation cache when compilation failed.
For example, if I create a JSP containing nothing but Hello, <%=world%>!
, predictably, I get an error: org.apache.jasper.JasperException: Unable to compile class for JSP
. Subsequent requests however alternate between this and org.apache.jasper.JasperException: org.apache.jasper.JasperException: Unable to load class for JSP
.
Further, if I create a JSP containing Hello!
, it of course works just fine. If I modify it contain Hello, <%=name%>!
, the response alternates between the previously-mentioned compilation error, and the cached Hello!
.
What's going on?
© Server Fault or respective owner