we're hosting a webservice that runs with up to 9 worker processes in it's application pool. There's a memory limit configured for the application pool to keep the system/server performant. Now my concern is that, if the memory limit is reached, a worker process may be recycled although there is an active request handled by this worker process that needs to be responded/finished first. The problem is especially with purchase/order requests, as such requests typically run several minutes and must not be aborted by any worker process recycle process. Is there any configuration setting that allows me app pool recycling by granting that no active process will be abandoned? Any advice appreaciated!
View Complete Post