more info....This doesn't seem too good and I should probably post to the
tomcat list on this
Looking at PageContextImpl, it has hidden another exception I believe.
521 } else {
522 // Otherwise throw the exception wrapped inside a
ServletException.
523 // Set the exception as the root cause in the ServletException
524 // to get a stack trace for the real problem
525 if (t instanceof IOException) throw (IOException)t;
526 if (t instanceof ServletException) throw (ServletException)t;
527 if (t instanceof RuntimeException) throw (RuntimeException)t;
528 if (t instanceof JspException) {
529 Throwable rootCause = ((JspException)t).getRootCause();
530 if (rootCause != null) {
531 throw new ServletException(t.getMessage(),
rootCause);
532 } else {
533 throw new ServletException(t);
534 }
535 }
536 throw new ServletException(t);
537 }
Notice stack trace below says line 533. This line is passed an exception I
do want to know about, but the root cause is supposedly that
ServletException, which is a mistake. The root cause is "t" or if t is
chained further, something that caused 't'. Don't suppose anyone knows this
one?
thanks,
dean
----- Original Message -----
From: "Dean Hiller" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 09, 2004 10:07 PM
Subject: org.apache.struts.action.MESSAGE not found??
I saw one long posting on this in the archives with no clear answer.
Someone had the exact same problem. For some reason PageContextImpl is
looking for a key I never defined and don't have in any of my jsp's.
Relevant stack trace is below...
I believe this is the only relevant part of the stack trace...
javax.servlet.ServletException: Cannot find message resources under key
org.apache.struts.action.MESSAGE
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:533)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:95)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
Line 95 of the index_jsp is having trouble. Here are the lines in the
generated index_jsp file from tomcat....
91 } catch (Throwable t) {
92 out = _jspx_out;
93 if (out != null && out.getBufferSize() != 0)
94 out.clearBuffer();
95 if (pageContext != null) pageContext.handlePageException(t);
96 } finally {
97 if (_jspxFactory != null)
_jspxFactory.releasePageContext(pageContext);
98 }
Notice the root cause of the real exception caught by line 91 is hidden by
the exception coming from line 95. (ie. I need to fix 95 and them I am off
on my own fixing my next problem. I really need to fix this one as I need
the errors my apps cause to be reported correctly. Anybody have any ideas
on this?
thanks,
dean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
