Hi, i'm currently working on an already existing project which is written in ASP.NET 5. In this there is a form on which is a button. This button gets pressed many times (up to 400 times within 3 hours approx). Today i made an automated test run for 6 hours in which the button was pressed roughly 1000 times. Suddenly the post method for the form in which the button is placed was not reachable anymore. I'm using Windows Server 2012 with IIS 8. My form looks like this:
@using (Html.BeginForm("PerformanceControl", "Performance"))
{
<div class="col-md-12 col-sm-12">
<button name="button" src value="forwardRecord" class="btn btn-primary">
Next Chunk class="fa fa-arrow-circle-right">
</button>
</div>
}
The receiving post method looks like this:
[HttpPost]
public IActionResult PerformanceControl(int id, string button, ShowPerformanceControlViewModel viewModel)
{
return RedirectToAction("PerformanceControl");
}
I have left out the logic code because it's a very big method.
The POST and GET method of the performance control are getting called with the same URL pattern: "/Performance/PerformanceControl/11" (the eleven is just an example ID).
The GET version of the call still works when the error occurs. I'm new to ASP.NET so i don't really what could be the reason for this strange behaviour especially when it worked 1000 times in the same session and the session data was not lost. The endpoint was only not reachable anymore?
Update:
I have now managed to recreate the problem and at first i thought it was the POST request but it turns out that the GET request after processing the form data fails, but when i hit reload the site works. Is there a common problem with redirect in ASP.NET?
P.S.: Sorry for my bad englisch, my native language is german.
What I have tried:
I have looked through all the logs of the server the only thing i could find was that after 14:20 (20.06.2018) every post request to post Method of the form didn't work anymore. Every other form on my website e.g. Login and Registration form did still work without a problem. I have also looked through the window event viewer but i could not find any suspicious entries. Only a restart of the asp.net site brought the form back to life. I also checked if there are database errors but there arent.