well; you could always write your own logging-routine/class... and then in
your code handle exceptions similar to the example-"code" below:
try
{
/* lot of important code */
}
catch ( ExceptionYouWantToCatch excp )
{
new LogFile( excp.getMessage(), logFilePath );
}
there's also been a lot of talk on how to do the logging in tomcat... as far
as i know, no one has successfully logged everything they intended to log
(by configuring the supposed files) or perhaps it's just me ;)
Best Regards & Good Luck,
//Adrian Papari.
-----Original Message-----
From: Nik Makepeace [mailto:[EMAIL PROTECTED]]
Sent: 02 February 2001 16:56
To: [EMAIL PROTECTED]
Subject: RE: Logging problems
On 2 Feb 2001, at 16:09, Adrian Papari wrote:
> how do you handle the exceptions? if you, for instance, redirect the
> user to an error page when an error occurs, you (or, erm, the user )
> shouldn't see the internal error messages.
They aren't 500 errors, but rather conscious decisions to write to
System.err in the source for the servlets. Basically, we are using
System.err to write debug for our servlets.
Jserv used to pick up System.err and send it to its error log, but it
seems like Tomcat doesn't behave this way. Any clues? We are really
stumped.
Nik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
