ASP .Net multiple Application Pools, and log file locking

[Martin Robinson]

I have Shibboleth SP running under IIS 6.

My Default Web Site contains a number of ASP .Net applications running under several Application Pools. 

This results in multiple copies of the Shibboleth ISAPI Filter being loaded - one per w3wp process. This seems to result in the native.log file growing indefinitely, and the automatic rollover of log files (as configured in native.logger etc) does not happen.  This is because there are multiple open handles to these files, and no process can rename/delete these files due to the open handles from the other processes.

I believe that log4j has a 'MinimalLock' locking mode that might get round this? How do I configure this in native.logger, or is there a better solution?

Thanks,

Martin Robinson