IIS 7 and Above
FastCGI update KB967131 question
Last post May 29, 2009 01:38 PM by ksingla
May 29, 2009 09:27 AM|Mike Ayling|LINK
Just curious about this update:
FIX: The FastCGI module does not work if you are using the HWC functionality of IIS 7.0 and the process that hosts the HWC is part of a Windows job object
What I'm wondering is if this hotfix eliminates the call that maintains a worker processes' child fast cgi processes within a job object? If that is the case, does this enable the ability to use the FastCGI module in conjunction with app pool cpu limits?
Am I wrong that w3wp worker processes are effectively HWC instances? If that is the case, would child FastCGI processes created by a w3wp or an HWC process remain resident after the parent process exited?
May 29, 2009 01:38 PM|ksingla|LINK
No, this hotfix doesn't eliminate the call to make child process part of fastcgi process job object and FastCgi still won't work when CPULimit is enabled. We are in process of releasing another hotfix which will actually make FastCGI work with CPULimit feature.
Even with the new hotfix, child processes are still part of a job object to make sure there are no zombie processes after w3wp.exe dies. To make sure CPU accounting is done right, we make FastCGI module report CPU usage of child processes to WAS.