I have an app hosted on IIS 8.5 which does not support multithreading. In Advanced Setting of the app pool I set
Maximum Worker Processes to 1 and set Disable Overlapped Recycle to
True. But I think this setting is not considered when Bin directory or web.config changed - new worker process is created while the old one is still alive, which is causing the app to crash.
Question:
How to fully disable overlapped recycle so that I am sure that new worker process for the application is created only after the old process
finished completely?
None
0 Points
2 Posts
Disable overlapped recycle when binaries changed
Apr 10, 2018 07:45 AM|Jakub.Ledworowski|LINK
I have an app hosted on IIS 8.5 which does not support multithreading. In Advanced Setting of the app pool I set Maximum Worker Processes to 1 and set Disable Overlapped Recycle to True. But I think this setting is not considered when Bin directory or web.config changed - new worker process is created while the old one is still alive, which is causing the app to crash.
Question:
How to fully disable overlapped recycle so that I am sure that new worker process for the application is created only after the old process finished completely?
All-Star
47870 Points
17751 Posts
Re: Disable overlapped recycle when binaries changed
Apr 10, 2018 08:13 AM|PatriceSc|LINK
Hi,
Are you 100% sure a new process is created before the old one is terminated ? And that this is what causes the crash you see ?
For advanced IIS questions, https://forums.iis.net/ might be better.
None
0 Points
2 Posts
Re: Disable overlapped recycle when binaries changed
Apr 11, 2018 09:57 AM|Jakub.Ledworowski|LINK
Actually, I found out that it is not a new process, but new Application Domain. And yes, I am 100% sure :)
I moved this question to:
https://forums.iis.net/p/1238380/2140376.aspx?p=True&t=636590121401031587