See http://jakarta.apache.org/tomcat/faq/logging.html#catalina.out
ClientAbortExceptions are thrown by tomcat when the client presses stop
before the page is downloaded but does not log the exception. If there is
custom code trapping exception - it might be logging it. In this case - the
custom code is too agressive in catching exceptions and should let the
container handle them correctly. (And probably incorrectly using
error.printStackTrace() instead of a logger)
-Tim
[EMAIL PROTECTED] wrote:
How do you limit the size of Tomcats stdout file.
If you look at version 5.5, the dialog for the service lets you put in
default or some path for the stdout file.
But there is no option to set the limiting size or other parameters as you
would with log4j.
This is the stdout log file which tomcat logs to if it gets something like a
network connection reset error.
This is not really the applications log file per se.
I tried asking this to the tomcat team via bugzilla and they were not
helpful.
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
