we've got some old legacy web apps that we host on an azure VM. In some circumstances they get stuck in a situation that spins the W3WP process into 99%> and causes grief for the server. They're not mission critical so it's safer for us to auto kill these processes when this occurs rather then opening up the code and changing old code.
We've tested the IIS Limit process functionality locally and it works perfectly, after 3 minutes of the process running > 90% the w3wp process is killed.
<cpu limit="90000" action="KillW3wp" resetInterval="00:03:00" />
I run the exact same settings on the VM in azure and it doesnt do anything. The process will continue to run high and IIS wont kick in and kick it out.
Any ideas?