#124 logfile.maxsize ignored

[Anonymous]

The logfile does not roll when its maximum size (in
wrapper configuration file) has been reached during
the running of the wrapped application.
If i restart the wrapper, then it rolls the logfile
at startup because the maxfilesize has been reached.
My application is ment to run continuously for ages..

WinXP 2002 SP1, java 5, integration method III

snippet from configfile:

wrapper.console.format=M
wrapper.console.loglevel=INFO
wrapper.logfile=C:/temp/gti/log/hostmanager/hostmanage
r.txt
wrapper.logfile.format=M
wrapper.logfile.loglevel=INFO
wrapper.logfile.maxsize=10000000
wrapper.logfile.maxfiles=10
wrapper.syslog.loglevel=NONE

contact: JStuijt@gti-group.com

[Leif Mortenson]

Logged In: YES
user_id=228081

The log rolling mechanism works by attempting to rename the
log file and then logging to the base name. If the rename
fails for any reason, rather than stopping logging, it will
just continue to append to the original log file. It will
continue to attempt to rename the log file on each log entry.

I have seen this is the past when a tail tool is being used
to monitor the log file. It has the file opened in a
non-locking read mode. But that is enough to prevent the
system from allowing the file to be renamed.

Cheers,
Leif