Re: ASP.Net recycles automatically every 180 seconds.

From: Shishir (shishir_g12@hotmail.com)
Date: 08/15/02 

From: shishir_g12@hotmail.com (Shishir)
Date: 15 Aug 2002 10:10:54 -0700

Hi Jeremy,

The flag u looking for deadlock response time is in machin.config
file.
this file control yours all machine level setting for .NET
environment.

so if you open machine.config file and look for "<processModel"
tag...u will find this tag eith all this attributes.

<processModel enable="true" timeout="Infinite" idleTimeout="Infinite"
shutdownTimeout="0:00:05" requestLimit="Infinite"
requestQueueLimit="5000" restartQueueLimit="10" memoryLimit="60"
webGarden="false" cpuMask="0xffffffff" userName="SYSTEM"
password="AutoGenerate" logLevel="Errors"
clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect"
comImpersonationLevel="Impersonate"
responseRestartDeadlockInterval="00:09:00"
responseDeadlockInterval="00:03:00" maxWorkerThreads="25"
maxIoThreads="25"/>

and if u see there is an attribute called "responseDeadlockInterval"
go there and increse the time limit and save this machin.config file
and don't forget to restart ur IIS service or IIS. because the changes
only reflect when u restart ur IIS service or some time OS also so go
ahead.

Just mail me if u able to do this.

Thanks.
Enjoy.
--Shishir
"Jeremy Morrissey" <jeremy.m.morrissey@intel.com> wrote in message news:<258701c243bd$e6025e30$3aef2ecf@TKMSFTNGXA09>...
> How to disable ASP.Net from recycling because "it was
> suspected to be in a deadlocked state. It did not send
> any responses for pending requests in the last 180
> seconds" (seen in event viewer logs). This occurs when
> an ASPx page that I've written sits idle waiting for the
> backend to respond for more than 180 seconds. There are
> business processes that take longer than 180 seconds
> (such as searching for backlogged orders in a large
> company). I agree that performance tuning is necessary
> on the backend, but when this is mission critical and end
> users are accepting this slow response time, we need a
> way to resolve the above solution before migrating
> to .Net.
>
> I've looked throughout the registry and metabase for some
> flag or value that I can increase, but I cannot find
> anything.
>
> Suggestions on how to bypass this condition or solutions
> around this would be much appreciated.
>
> thanks

Quantcast