So in answer to my question then there is no way to actually 'delay' the
destroying of the old worker process while new requests are sent to a new
worker process, in other words recycling the worker process is pretty much
the same as scheduling an IISReset on the server?
Simon
"John Cesta" wrote:
> On Mon, 24 Jan 2005 03:07:03 -0800, "geeza105"
> <geeza105.RemoveThis@discussions.microsoft.com> wrote:
>
> >Hi,
> >I have an app that has a large memory leak and was told that I could use the
> >worker process recycling setting to reset the worker process when it breaches
> >a certain memory usage. This works fine but unfortunately it drops all of the
> >current open session variables when it recycles itself (understandably), but
> >is there any way of still recycling the worker process, but keeping the
> >distressed worker process open for a specified time limit, say 20 minutes for
> >example, rather than destroying it straight away (therefore giving users of
> >the app time to finish what they are doing before they get new session data?)
> >
> >Thanks
> >
> >Si
>
>
> When you reset the worker process everything gets reset. It's all or
> none.
>
> John Cesta
>
> The CPU Checker - Monitors your CPU % while you sleep
> LogFileManager - IIS LogFile Management Tool
> WebPageChecker - Helps Maintain Server UpTime
> DomainReportIt PRO - Helps Rebuild IIS
<font color=purple> > <a style='text-decoration: underline;' href="http://www.serverautomationtools.com</font" target="_blank">http://www.serverautomationtools.com</font</a>>
>
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Recycling the worker process for ASP 3.0 applications in I..