Hi David.
I had this problem
My solution was edit server.xml and change the verbosityLevel of
jasper.log. See:
change to:
In the FATAL mode, jasper.log only records the fatal errors and no
more causes it problems.
Bye.
On Mon, Feb 12, 2001 at 01:28:13PM -0300, [EMAIL PROTECTED] wrote:
>
>
> Hi David.
>
> I had this problem
>
> My solution was edit server.xml and change the verbosityLevel of
> jasper.log. See:
>
> In the FATAL mode, jasper.log only records the fatal errors and no
Title: RE: refresh/flush logs question
You did not mention the platform, but if you are on unix, you can use
cp /dev/null tomcat.log
to 'null' out the logfile. This sets the file to be 0 bytes without interrupting the process using it.
Most processes do not have a problem with
