Description
Describe the bug / Steps To Reproduce
I have a Asp.Net Full Framework MVC Application (Visual Studio default MVC Template) hosted on my local IIS10 (Win10) (not IIS Express) with "Disable Overlapped Recyle = false" (default value).
If i recycle the application pool while i use a tool to continuously send http requests the webserver will respond correctly for all requests, no Errors (500 / 503) and no timeouts.
If i try to do the same with Asp.Net Core 2.2 (InProcess) i will get 503 exceptions.
I have the same Problem if i change the physical path for my website.
Full Framework no 503, AspNetCoreModuleV2 a lot of 503.
The old "AspNetCoreModule" (Asp.Net Core 2.1) had a similar Problem but had returned less 503 responses.
Expected behavior
The Expected behavior would be:
- no 503 errors on recycle (with "Disable Overlapped Recyle = false")
- no 503 responses if the physical path changes.
This is important for high availability and depoyment in my case.
Screenshots
Full Framework 4.7.2 with overlapped recycling not hosted via AspNetCoreModule
(left Baseline, right recycle test)
AspNetCore 2.2 with overlapped recycling via AspNetCoreModuleV2
(left Baseline, right recycle test)