https://issues.apache.org/bugzilla/show_bug.cgi?id=47717
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Mark Thomas <ma...@apache.org> 2009-12-14 02:31:54 GMT ---
You will see this if the JSP was compiled, Tomcat restarted and then the JSP
requested. Since the new Tomcat instance didn't compile the JSP, pageNodes will
be null - hence the NPE.
This is handled by falling back to the error handling that does not display the
relevant JSP line numbers. This error page should show:
- the exception and any root cause
- the line number of the Java file where the error occurred
It shouldn't be too hard to look in the Java file and manually trace the error
back to the appropriate line in the JSP.
This could be handled more cleanly rather than relying on the NPE but I can't
find any bug here.
If you have a JSP that triggers this where the appropriate stack traces are not
shown in the browser then please feel free to re-open this bug and attach your
JSP so we can investigate further.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
