Hi,
If you go to the processModel in your machine.config file (default
location>C:\WINDOWS\Microsoft.NET\Framework\v1.1.4 322\CONFIG) it has a
setting...
<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"
responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/>
Now, the memoryLimit = 60 signifies the percentage of memory which could be
reached before a process recycles. There could be some memory leak that is
happening in your application. Just ensure that you have debug="true" in your
web.config file for all the applications and see if that helps.
Thanks,
Rahul Soni
"Erkan Tatlidil" wrote:
Hi,
Our customer has a win2k Xeon 2.0 web server with 2GB of Ram. After a
certain time the aspnet_wp.exe consumes %70 of the Ram and comes to a
standstill. We end the process and everything is ok. We used memory profiler
to find out what is causing the problem but couldn't come to a result. I've
noticed that their is a patch for this type of cause on Microsoft's web site
but no download.
The framework is 1.1.4322
Cheers
Erkan Tatlidil