tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: [5.0] Servlet logging and error messages
Date Mon, 21 Jul 2003 12:51:07 GMT


>- Stripping out all the Catalina related part of the stack trace in the
>HTML generated by the ErrorReportValve; that eases debugging.

Hmm... As long as the full stack trace, including Catalina, is still in
the log file, that's OK.  I know the Catalina parts of the stack trace
frequently have <= 0 value, but I still feel better knowing the full
stack trace is there.

>- When an exception occurs, and it is a ServletException, I think the
>root cause should be logged, not the external exception, which 99% of
>the time is useless.

What about cases where someone constructs a ServletException with a
message, without a root cause exception?

>- I strongly believe that all webapp triggered logging (init errors,
>service errors, etc) should go to the servlet container provided logger
>(ie Context.getLogger()). 

Ditto, +1.

>Right now, a significant amount is sent to
>commons-logging. I was aware that the intent was to switch the
>itself to commons-logging (and I am +1 for it), but c-l or another
>generic logging framework such as log4j, is IMO not adapted to provide
>the webapp logging (same for the access log, obvioously).

Curious: why is log4j not adapted / what's missing from it for this

Yoav Shapira

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message