I have the following problem:
After an file update or a configuration change to one of the sites running on the iis server i need to kill all w3p.exe's running on that server in order to let the website/app-pool start again.
I have 2 servers and both servers have the same behavior, also the normal recycles don't work until all existing w3p.exe's (that not have been killed since the update)
the websites/app-pools start (i can see the w3p.exe in the task manager) but the sites don't actually start until i've killed the w3p.exe's.
At the moment i've killed the last active w3p.exe all sites start their warmup.
Has anyone encountered this before? it keeps me from using continuous integration since i have to manually kill all the app-pools after a release
The pools aren't in use at the moment of the recycle, i tried this by making them only accessible from the local machine which made sure i knew all the connections running on the pools
The pools do start after i killed all w3p.exe's or restarted the iis service, but after an file change or configuration change pools are not able to start after their recycle, they keep at 0 cpu until all pools have been killed.
The servers are running Windows server 2012 with the latest updates (although i have this problem for quite a while now, so it has been doing this before the latest updates too)