tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15974] - Original stack trace is lost
Date Tue, 03 Jun 2003 15:58:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15974>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15974

Original stack trace is lost

tomy@softwaredesign.com.br changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From tomy@softwaredesign.com.br  2003-06-03 15:58 -------
Please, read my original request again:

"As you can see, on the 4.1.18 version, the root cause does not show the stack 
trace entering the 'throwError' method of the class, as does the 3.3a version."

Tomcat gave me *a* root cause, but not *the* root cause I would expect. Take a
closer look at the root cause shown on Tomcat 4.1.18. From that, I wouldn't know
that the 'throwError' method of my class generated the exception. Compare the
two root causes I gave you:

On 4.1.x:

javax.servlet.ServletException: just testing
  at org.apache.jasper.runtime.PageContextImpl.handlePageException
(PageContextImpl.java:533)
  at org.apache.jsp.myError_jsp._jspService(myError_jsp.java:49)
[...]

On 3.3.x:

java.lang.Exception: just testing
  at com.eadweb.StackTraceTest.throwError(StackTraceTest.java:5)
  at myError_2._jspService(myError_2.java:53)
[...]

What's shown on both before the "_jspService" line? Is it equal? No! The second
one shows the stack trace for the original root cause before the "_jspService".
That's why the "throwError" method of my class appears on it. In the first one
(4.1.x), there's no information about my classes, but only about Tomcat's classes.

As I said, it seems that the original stack trace is lost, and it's very bad,
because knowing which of my classes generated the exception helps me much to fix
the problem.

Do you understand the problem now?

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message