Unfortunately in tomcat 4, it doesn't delve deep enough into the nested
exceptions such as Servlet exception to print the real root cause.
As to finding out the real error, see line:
org.apache.jsp.LMSCourseImport_jsp._jspService(LMSCourseImport_jsp.java:451)
Most important is LMSCourseImport_jsp
Two/three common exceptions with that sort of message are:
ClassCastException
ClassNotFoundException/NoClassDefFoundError
try putting scriptlets around the offending bit of jsp like this:
<% try {%>
<% } catch (Throwable t) {
e.printStackTrace(); // or whatever logging you are using ;)
Tim,
On Wed, 12 Nov 2003, Tim Funk wrote:
> Typically there are 2 (or more exceptions shown). Usually the "bottom most"
> exception is the one your most interested in since that what through the
> real exception. The reason is because the JSP catches an exception, wraps
> it in a JSPException,
Typically there are 2 (or more exceptions shown). Usually the "bottom most"
exception is the one your most interested in since that what through the real
exception. The reason is because the JSP catches an exception, wraps it in a
JSPException, and throws it where it is caught by the servlet eng
Hi All,
I'm getting a JasperException when I try and run some JSP code. The
main problem with fixing it is that I've no idea how to read the
traceback. It doesn't seem to give many clues as to what's going
wrong.
The full thing is at http://www.hellaweb.com/hellabot/415
I guess there should be s
