ASP .Net multiple Application Pools, and log file locking

[Marvin Addison]

>
> 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.


We recently struggled with this same problem in another context. Our
solution was to create a unique name for each daily log file, e.g.
native-2015-08-05.log, and avoid rollover altogether in the logging engine.
Testing showed the logging engine (logback in our case) simply couldn't
handle rollover across separate processes in a reliable fashion without
configuration options that dramatically impacted performance and even then
didn't guarantee correct behavior. Of course it's possible log4j may be
more capable in that regard, but I doubt it.

M <dev-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150805/224b62f7/attachment.html>