avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leif Mortenson <leifli...@tanukisoftware.com>
Subject Re: [Fortress] Minimizing stack traces on startup.
Date Thu, 12 Jun 2003 04:29:07 GMT
Rather than this:
getLogger().error( msg, e );

I do this:
getLogger().error( msg + " : " + e.getMessage() );
getLogger().debug( "Stack Trace:", e );

Or something along those lines.  It really depends on the context.


Anton Tagunov wrote:

>Hello Leif!
>LM> The stack traces are obviously invaluable during development and even
>LM> for debugging problems in a deployed application.
>LM> But they also need to be invisible to the end users.
>LM> I usually do this on a component level by only showing stack traces at the
>LM> debug priority.
>Very interesting!
>What I do, I have a number of expected exceptions that I know
>I won't need a stack trace for (f.e. ConfigurationException)
>and do it like this

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

View raw message