Prev: WCF service - netTcp binding - Server Application Unavailable mess
Next: Is there a way to change the app domain recycle settings programmatically or in the registry?
From: Bob on 21 Apr 2010 16:43 We run IIS 6.0 on server 2003 SP2 32bit OS. I seethe following in the event viewer system log --- A process serving application pool 'DefaultAppPool' exceeded time limits during shutdown. The process id was '3412'. I hear from users that get disconnected off their web application intermittently - could be once a week/more/less.... I'm wondering if this message could cause people to get bumped off their web application. if not --- we need to look elsewhere as to what may cause the intermittent disconnect off users web application. If this can be a problem - message should not be shown --- can you tell me how to correct ? Thanks, Bob
From: Dan on 22 Apr 2010 06:09
"Bob" <Bob(a)discussions.microsoft.com> wrote in message news:73F61A25-56CD-4114-85F1-98F9A858DD39(a)microsoft.com... > > We run IIS 6.0 on server 2003 SP2 32bit OS. > > I seethe following in the event viewer system log --- > > A process serving application pool 'DefaultAppPool' exceeded time limits > during shutdown. The process id was '3412'. > > I hear from users that get disconnected off their web application > intermittently - could be once a week/more/less.... I'm wondering if this > message could cause people to get bumped off their web application. if not > --- we need to look elsewhere as to what may cause the intermittent > disconnect off users web application. > > If this can be a problem - message should not be shown --- can you tell me > how to correct ? > > Thanks, > Bob > > It won't be that message specifically, but that appears to be a result of the process recycling. Check the IIS application pool properties, and if you don't want the process recycled while your users are on it then adjust the recycling settings. That event log error does however point to an issue - when IIS tries to recycle the application pool process, something is causing the process to not be able to shutdown within the configured time allowance. You'd need to look into what is stopping the process from shutting down. -- Dan |