The last time I came upon this problem had to do with a situation where the
server spiked pushing it over its memory limit. I think the only approach
that worked was to repair the ill code. How about setting some other recycle
"Julian Jelfs" <JulianJelfs@discussions.microsoft.com> wrote in message
news:24B1750F-515B-43EE-B59A-3628F64BDA35@microsoft.com...
> Hi,
>
> I have a problem with a windows 2000 server running version 1.1 of the
..Net
> framework. The symptom is that memory usage by the aspnet_wp process
> gradually increases until the web application I'm running becomes
> unresponsive. The server has 4GB of RAM and the application becomes
> unresponsive at about 800 to 1000MB. I understand that the limit before
the
> worker process recycles should be either the 60% of availabel memory
> specified in the machine.config or 800MB whichever is less.
>
> The main question here is why is the aspnet_wp process not recycling? It
> just stops working but doesn't recycle. Obviously there may be a secondary
> issue regarding memory usage in the application but I think I could get
away
> with that if the process recycled as it should. Also I have been
completely
> unable to recreate this behaviour on other machines.
>
> The only thing I have found which might it explain this is the following
> support article
>
>
http://support.microsoft.com/default.aspx?scid=kb;EN-US;330469 >
> but it appears to refer to version 1.0 of the .Net framework. Could this
> still be the issue that I'm seeing and is it worth applying this hotfix?
My
> only alternative at the moment is to try to rebuild the server and that
would
> cause major disruption.
>
> Thanks in advance,
>
> Julian.