Have you upgraded to log4j-1.2.15? That should eliminate the loss of
earlier messages on a failed rename.
Then you need to figure out why the rename is failing. Are each of
your web applications writing log files in a different location? It
appears you are attempting that in your configuration file, but is
that actually happening. If you have multiple apps writing to the
same location, bad things are likely to happen. You could use lsof
on 'nix or Unlocker or SysInternal's Process Monitor on Windows to
see what processes may have the file open.
If not, are the privileges set so that the account that is running
Tomcat has the necessary rights to rename the file.
Does the target file exist, if so they access control should be set
to allow log4j to delete the file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
