worker-process

I have a very weird problem with one of my IIS application pool processes. Ive been getting a System.OutOfMemoryException error lately and ive been trying to figure out exactly what is going on. Basically I have a script that uses a web service to get a file from our DAM. It then checks the file stores it a byte array, then uses the Response to output the file. The only one ive been having problems with is the PDF's when they are over 20MB now it seems that they cause an error sometimes. If I increase the memory in the app pool it fixes the problem temporarily. I watched the w3wp.exe process

In IIS7 Application Pool there is a setting Idle-time out default is 20 min, which says: Amount of time(in minutes) a worker process will remain idle before it shuts down, A worker process is idle if it is not processing requests and no new requests are received. My question is, if the worker process shut down because of the time-out time, does the session created by application which is hosted in this worker process get lost? Yes -- the session data is tied to the app pool worker process , so once the worker gets shut down, the session data is lost. The default behavior is to store session

My project loads significantly faster when I attach it to my w3wp.exe IIS worker process, than when I "Start Debugging". However, the same worker process seems to be processing the same amount of modules/DLLs (w3wp.exe) whether I "Start Debugging" or "Attach to Process". Why is attaching to a process so much quicker? Rudolfs Bundulis "Start Debugging" launches a new instance of the executable with the debugger attached right from the beginning, so the overhead of all the needed debugger calls is incurred from launch, whereas "Attach to Process" attaches to a already running process, so until

How do you increase the number of threads per worker process in IIS? Using IIS this can be done. I searched everywhere, so I decided to put this out here for everyone to use this information. Click on the server. Then on the right side pane, double click on ASP. Increase the number of threads per processor Using config files For example: %windir%\Microsoft.NET\Framework64[version]\config\machine.config <configuration> <system.net> <connectionManagement> <add address="*" maxconnection="24" /> </connectionManagement> </system.net> <system.web> <processModel autoConfig="true" maxWorkerThreads =

I've noticed that on one of my production web apps, when I manually recycle an app pool, the recycled worker process can take upwards of 60+ seconds to actually be completely destroyed, based on watching it in Task Manager. However, if I stop the app pool completely, the worker process goes away nearly instantaneously - within 1-2 seconds. So, my question is two-fold: a) Why does it take so long to destroy the process (and more meaningfully, release the resources used/locked by it) when the app pool is recycled instead of stopped; and b) Assuming that I've stopped traffic from being directed