Tim, On 6/2/21 14:53, Tim Funk wrote:
My guess? ClassNotFoundException is rooted in some other exception. Such as a different error is thrown during class initiation. Such as a static { doStuff();} block where doStuff does bad stuff.Hopefully there is more stack trace out there. If the JSP has static initializers - wrap them in try {} catch blocks{} even if you think they don't need wrapped in those blocks.
I can try that, but I was wondering about getting more information at runtime since the system is currently angry. I'm willing to bet that if I restart Tomcat, the error will go away.
This JSP hasn't been changed since 2016, and it's pretty reliable :) Thanks, -chris
On Wed, Jun 2, 2021 at 1:53 PM Christopher Schultz < ch...@christopherschultz.net> wrote: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 java.net.URLClassLoader.findClass(URLClassLoader.java:382) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:128) at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:59) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:159) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:192) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:413) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) [...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.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
