Skip to content

IIS AspNetCore Module V2 returns 10s of 503 error and "Failed to gracefully shutdown applicaiton" warning when recycling a Hello world demo #49350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
AlexChongMicrosoft opened this issue Jul 12, 2023 · 8 comments
Assignees
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions investigate

Comments

@AlexChongMicrosoft
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

1.There is a demo adding a simple function manageloop() in a helloworld.cs.
2.When using .net framework 4.7.2, everything is good.
3.When using .net core 6, it returns around 10s of 503 error and "Failed to gracefully shutdown applicaiton" warning when recycling.

Expected Behavior

The asp.net core 6 app should shut down gracefully and returns 200.

Steps To Reproduce

I have the demo running in my lab.
1.Publish the web app demo to IIS.
2.keep sending Get requests to the IIS site.
3.Recycle the appilcation pool.

Then 503 is got in the postman which sends reuqests. "Failed to gracefully shutdown applicaiton" shows in the event viewer log.

Exceptions (if any)

No exception.

.NET Version

I target it to .NET 6. I have .NET 7.0.203 as the runtime

Anything else?

This is the event viewer warning.
image

This is the 503 returned by postman
image

This is the freb of 503, which indicates the 503 is returned from IIS
image

I have the demo and lab. Please contact me to demo it. If any further information is needed. Please let me know.

@ghost ghost added the area-runtime label Jul 12, 2023
@AlexChongMicrosoft
Copy link
Author

Searched and found a similar report as #41340.

@adityamandaleeka
Copy link
Member

@BrennanConroy PTAL

@AlexChongMicrosoft
Copy link
Author

@adityamandaleeka thanks a lot for your prompt reply.

@BrennanConroy I have the demo and lab to show the issue. If you wish, we can have a discussion. Let me know if something I can do.

@AlexChongMicrosoft
Copy link
Author

@adityamandaleeka @BrennanConroy how are you? Look forward to your feedback. Please let me know if some informtion is needed.

@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 25, 2023
@AlexChongMicrosoft
Copy link
Author

Thanks for your warm hands ASP.net core team. It has been confirmed a design of ASP.net core.

@cun-dp
Copy link

cun-dp commented Aug 28, 2023

Thanks for your warm hands ASP.net core team. It has been confirmed a design of ASP.net core.

Hi Alex,

I'm coming from #41340. Does that mean that this is an intended design of ASP.net core?
Will there be any fix for this issue? Or will overlapped apppool recycle never be supported by ASP.net core on IIS?

Thanks and best regards

@luizfbicalho
Copy link

Hi Alex,

I'm coming from #41340. Does that mean that this is an intended design of ASP.net core? Will there be any fix for this issue? Or will overlapped apppool recycle never be supported by ASP.net core on IIS?

Thanks and best regards

I think that could be nice if The aspnet team give a complete status.
What are the alternatives?
Linux?
Docker?
Change the overlap?

I have one project that suffers from this and the customer would be a lot happier with an official information.

@BrennanConroy
Copy link
Member

This looks like a dupe of #41340, closing.

@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions investigate
Projects
None yet
Development

No branches or pull requests

6 participants