Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [5.0] Servlet logging and error messages
Date: Mon, 21 Jul 2003 08:51:07 -0400
Message-ID: <9C5166762F311146951505C6790A9CF8346471@US-VS1.corp.mpi.com>
Thread-Topic: [5.0] Servlet logging and error messages
Thread-Index: AcNNe1RElxsaKB4rTMOizvGaSm0Y5gCCppaw
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>


Howdy,

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

Hmm... As long as the full stack trace, including Catalina, is still i=
n
the log file, that's OK.  I know the Catalina parts of the stack trace=

frequently have <=3D 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 logg=
er
>(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
container
>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 provid=
e
>the webapp logging (same for the access log, obvioously).

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

Yoav Shapira


This e-mail, including any attachments, is a confidential business com=
munication, and may contain information that is confidential, propriet=
ary and/or privileged.  This e-mail is intended only for the individua=
l(s) to whom it is addressed, and may not be saved, copied, printed, d=
isclosed or used by anyone else.  If you are not the(an) intended reci=
pient, please immediately delete this e-mail from your computer system=
 and notify the sender.  Thank you.


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