The JSP has not been deleted and a stack trace is logged like:
org.apache.jasper.JasperException: Le fichier "/xxx/yyy/zzz.jsp" n'a pas été
trouvé
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
at
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
at
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
at org.apache.jasper.compiler.JspUtil.getInputStream(JspUtil.java:849)
at org.apache.jasper.compiler.JspUtil.getReader(JspUtil.java:1084)
at
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:250)
at
org.apache.jasper.compiler.ParserController.parseDirectives(ParserController.java:120)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:165)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:332)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:312)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:299)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
This particular example occurred on a system running in a French locale,
but translates into "The file ___ was not found".
Why a JSP that has already been compiled is being recompiled is another
question I have...
--
Jess Holle
On 12/16/2010 7:08 AM, Konstantin Kolinko wrote:
2010/12/16 Jess Holle<je...@ptc.com>:
Has anyone seen issues with JSPs that are present in an expanded web app
directory (i.e. deployed with an XML file pointing to a directory in WAR
layout rather than as a WAR) being found by Tomcat for a long time, weeks
even, and then suddenly no longer being found thereafter?
What are the symptoms? just 404? class not found (500) ?
Tomcat 6 will return 404 if the webapp is unavailable (undeployed, stopped).
Maybe that is your cause?
In the changelog there is
"When development mode is enabled and a JSP is deleted, ensure next
request for that JSP is consistent with the JSP having been removed."
in 6.0.21 (r832102)
http://www.mail-archive.com/dev@tomcat.apache.org/msg35608.html
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
