This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 21%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello,
We are hosting an ASP .NET Core 6 application on IIS 8.5 Windows Server 2012 R2. This application provides Microsoft.AspNetCore.Mvc.Controllers to an Angular application. One of the supported calls can take quite a long time (10-15 minutes). Now with this call we are experiencing some unfortunate unwanted behavior. Looking at the browser call I can see that the call is executed exactly once, it runs for about 7-8 minutes, then it fails with net::ERR_EMPTY_RESPONSE.
If I look at the server log however I can see that Microsoft.AspNetCore.Hosting.Diagnostics reports the call to be started again after several minutes have elapsed. Both calls actually seem to finish successfully but since they are POST calls creating data this is absolutely not what we would want to happen. So I've tried to find some info about this and there were very few posts that sounded kind of similar and none had an answer that helped so I'm hoping you can help me.
My first question is what is causing the call to be exectued again? We haven't implemented anything like that, the frontend isn't triggering it, when I debug locally with IIS Express I can't reproduce it so I'm assuming it might be an IIS 8.5 feature but I'm unsure.
The second question is how could I allow for requests to be running that long. I've already tried increasing httpRuntime executionTimeout and aspNetCore requestTimeout. I've also tried to increase the timeout of the Web Site in IIS and changed some settings of the Application Pool. Another thing I tried was to change the hostingModel from InProcess to OutOfProcess. Nothing changed the behavior I've described.
Any help would be greatly appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 24%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
@SAB
You can try to use failed request tracking to view the detailed process, and the generated log file will have the call process and time spent at each stage.
People are not able to help you on the first question without knowing more about the web app itself. That often requires server access and code access. So, if your company has a support contract with Microsoft, open a support case via https://support.microsoft.com.
The second question is also impossible to answer. Allowing a request to take minutes to finish only makes your web app vulnerable to attacks like DOS and the web server can be easily exhausted. You would have to complete redesign the web app. The answer below gave you some hints, but if you look for examples Microsoft support might also show you a few (depending on the support contract you are on).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
15 minutes is too long. you should change to a background request, and polling for the response, or use websocket which supports long connections.
Thanks for your answer, I'll look into the suggested options.
So I can see that such a long running request is not the intended use case but I'd really still like to know what is causing the request to be repeated and how to avoid this. Any clue regarding this.
You would need to do a network trace to determine where the duplicate request is coming from. Most likely it’s the angular app but it could be a proxy or load balancer.