ASP .Net multiple Application Pools, and log file locking

[Martin Robinson]

To add whatever is necessary to log4shib and isapi_shib.dll so that the log file handles are closed while that IIS process is idle, between http requests?

Doesn't sound like a big ask really.  Could be done simply by defining a new log appender class, derived from RollingFileAppender, but that opens and closes the file for each append. That might be too much of a performance overhead. It would be better to open the log file(s) once at beginning of each ISAPI event, handle the event (logging as much or as little as required) then close the log file(s).

Keeping open files handles for long periods is a BAD THING as it also prevents you clearing up log files manually. I needed to restart IIS on a production server to clear out a 500MB log file that I found to be growing rather quickly. 

Martin Robinson

-----Original Message-----
From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 05 August 2015 15:29
To: Shib Dev
Subject: Re: ASP .Net multiple Application Pools, and log file locking

On 8/5/15, 9:00 AM, "dev on behalf of Martin Robinson" <dev-bounces at shibboleth.net on behalf of martin.robinson at dai.co.uk> wrote:



>Perhaps someone on the Shibboleth team could come up with a better logging mechanism? 

Which would be?

-- Scott

-- 
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net