You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/04/16 01:30:37 UTC

DO NOT REPLY [Bug 19049] New: - Nested Exceptions result in confusing error messages

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=19049>.
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=19049

Nested Exceptions result in confusing error messages

           Summary: Nested Exceptions result in confusing error messages
           Product: Tomcat 4
           Version: Nightly Build
          Platform: Other
               URL: http://p1.selectacast.net/~jks/pci-patch.txt
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jks@akula.com


Just reusing the message from the nested Exception loses the context of the
message.  This is making it impossible to debug certain Errors.  For example
"java.lang.NoClassDefFoundError: com/x/y/ClassName" turns into:
"javax.servlet.ServletException: com/x/y/ClassName" which is much less helpful.
 This patch is just the first step, the second is to have the dynamically
generated error page unnest all levels of Throwables, right now it just unnests one.

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