I don't do too much work with JSPs, but I do have a few quick-and-dirty administrative things including one called the "session snooper" which just dumps out loads of information about the current user's session object.

I'm getting this error in production, and I can reproduce it every time I access the page. Here's the exception stack trace:

java.lang.ClassNotFoundException: org.apache.jsp.admin.SessionSnooper_jsp
at org.apache.jasper.servlet.JasperLoader.loadClass( at org.apache.jasper.servlet.JasperLoader.loadClass( at org.apache.catalina.core.DefaultInstanceManager.newInstance( at org.apache.jasper.servlet.JspServletWrapper.getServlet( at org.apache.jasper.servlet.JspServletWrapper.service( at org.apache.jasper.servlet.JspServlet.serviceJspFile(
   at org.apache.jasper.servlet.JspServlet.service(
   at javax.servlet.http.HttpServlet.service(
   [...filters, etc...]

This is a relatively simple JSP. There are no tag libraries in use and there are 3 imports of JSPs which contain some static utility functions.

Both files app/work/Catalina/localhost/[$context]/org/apache/jsp/admin/ and app/work/Catalina/localhost/[$context]/org/apache/jsp/admin/ exist and have file-dates from way back in 2016. (No recent changes)

The context has been restarted/reloaded (not redeployed) recently using JMX a few times, but nothing else relevant comes to mind.

This is Tomcat 8.5.65 from a stock ASF-distrubuted tarball, launched using " start". Nothing fancy.

What other information can I collect to help debug this? My expectation would be that the class should be findable and runnable. Tomcat should not be tripping over its own feet on this one IMO.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to