About the phenomenon where IIS worker processes start up more than the maximum number

Question

I am using Windows Server's IIS for a certain product. Recently, IIS worker process does not start up properly after recycling. An event has occurred. When I sent the event log to the product person and asked him to investigate,

• The maximum number of IIS worker processes is 1 ・Nevertheless, on the event log (system log), for the two worker processes, There is a log showing an attempt to carry out recycling. 　 The following example is a webhook log, and it shows that two worker processes are being recycled with a difference of 1 second. They said it looks like this. The worker process with process ID '532' in use by application pool 'Webhooks' needs to be recycled. The scheduled time for the process has been reached. The worker process with process ID '4776' in use by application pool 'Webhooks' needs to be recycled. The scheduled time for the process has been reached. However, even if you look at the number of worker processes on screens other than recycling (for example, the IIS screen), 1, and maybe there are multiple processes at the moment of recycling, but honestly I have no idea what the second one is. there is no. The person in charge of the product told me that it was not a problem with the product itself, so I posted it on this site. If anyone knows a solution to this kind of issue, please let me know

Answer 1

Hi there, Thanks for your post. Here are some suggestions to query the IIS procedure. Just for your reference and hope it is helpful.

1. Make sure this app has its own application pool, so that you can isolate what it's doing from any other processes.
2. As a stop-gap, maybe configure the pool to recycle after a max used memory of 2000 MB. This will be disruptive, but better than it using all the RAM and locking up.
3. Run Process Explorer from Sysinternal (Microsoft) while this is occurring. This will tell you a LOT of info about the process, including open file handles, GDI objects, etc.
4. Run Performance Monitor and look into the .NET CLR, Active Server Pages, and ASP.NET performance objects (as applicable to your application) to see if you can get some idea about what's doing the badness. Best Regards, Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

.I accidentally posted it in the answer section, so I deleted it.