--------------------------------------------------------------------------------

Every three or four days I have the reboot my web server because the performance becomes so slow , nothing will function. I traced the problem to the ASPnet_wp.exe. Using the task manager, I can watch as memory is being added to this exe each time I open or refresh my web pages, but I never see memory released. Eventually there will be so much memory consumed, the web server will slow right down to nothing.

Is there a way to release this memory or to configure the server so that ASPnet_wp.exe does not consume so much? Is there something I have to do in my applications to manage this memory?

You can modify the memoryLimit of the asp worker process (aspnet_wp.exe). The default value is 80 or 80% of memory.

Look for the <processModel> section of the machine.config file.

I forgot to mention that once it reaches the limit it automatically shuts itself down and a new worker process begins.

But the bigger issue is: what do you have that's causing this? I have found few to no memory problems with ASP.net when running native .net code. However, we encountered significant problems when we started using some pretty bulky old COM objects (with RCWs) in our .net code. This cause lots of memory leaks and eventual reboots.

Peter
------------------------------------------------------
Work smarter, not harder.

We have a similar issue, but our configuration includes an Oracle 9i database and we are using the ODP.NET driver to connect from ASP.NET to Oracle.

We have determined through research that aspnet_wp.exe will maintain a thread for each user login until the IIS services is recycled. This quickly grows the aspnet_wp.exe to a very large size and maxes-out the memory avilable to Oracle.

For every connection that is opened, one must conclude the method with close() and dispose(), or else the thread stays in perpetuity.