HTTP Error 503.0 - Server has been shutdown The service is unavailable. Most likely causes: An invalid identity in the application pool could cause this error. The application pool is no longer running because of configuration or reaching application failure limits. The concurrent application request limit was reached. #41771
Labels
area-networking
Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
Needs: Author Feedback
The author of this issue needs to respond in order for us to continue investigating this issue.
Is there an existing issue for this?
Describe the bug
I am hosting an asp.net core website on IIS having following recommended steps
It starts up fine and displays a list of inventory in an html table (jquery datatables)
being pulled from SQL server database and using Entity Framework. All good
BUT if I then refresh the same page once or twice or click the button to fetch the data again
"Service unavailable. 503.0. Server was shut down"
I have produced all the logs and none of them give an error besides a request and 503 response.
If I test using the kestrel URL I cannot reproduce the bug - so I don't think it's a code error.
Any ideas? Am I configuring something wrong? Where to look for answers?
Website in question is : https://stokseek.colms.net/
Thanks for any help!
Expected Behavior
I should be able to refresh the page as often as I want to without the service being shut down
In Kestrel on the server it all works fine
In IIS it breaks after a couple of refreshes
Steps To Reproduce
No response
Exceptions (if any)
No exceptions besides
"The service is unavailable."
"HTTP Error 503.0 - Server has been shutdown
The service is unavailable.
Most likely causes:
An invalid identity in the application pool could cause this error.
The application pool is no longer running because of configuration or reaching application failure limits.
The concurrent application request limit was reached."
.NET Version
.NET CORE 6.0
Anything else?
https://stokseek.colms.net/
The text was updated successfully, but these errors were encountered: