AspNetCoreModule icon indicating copy to clipboard operation
AspNetCoreModule copied to clipboard

Web app went idle after few days, even have "Always on" turned on

Open Tratcher opened this issue 7 years ago • 3 comments

From @ferrancg on October 6, 2017 20:12

I have an app running on Azure Web App, and I turned on the "Always on" in App Settings. After 5 days, the app went idle, and when I browse the web again, it will start up itself. There is no exception or error message in the log, so I assume the server or IIS shut it down. The following is the last entry of the log before shutdown:

2017-10-04 18:50:16.836 -07:00 [Information] Microsoft.AspNetCore.Hosting.Internal.WebHost: Request starting HTTP/1.1 POST http://127.0.0.1:31389/iisintegration  0
2017-10-04 18:50:17.542 -07:00 [Information] Microsoft.AspNetCore.Hosting.Internal.WebHost: Request finished in 1156.5419ms 202 

Any ideas what's going on? Thanks!

Copied from original issue: aspnet/IISIntegration#445

Tratcher avatar Oct 06 '17 20:10 Tratcher

@ferrancg See https://github.com/aspnet/AspNetCoreModule/issues/29 and https://github.com/aspnet/AspNetCoreModule/issues/63.

guardrex avatar Oct 06 '17 20:10 guardrex

Seems like the Application Pool idle timeout is configurable in IIS and can be set to infinite. If that is the case, it seems an issue in Azure web service, the "Always On" feature does not actually make the service always on.

ferrancg avatar Oct 06 '17 22:10 ferrancg

So how we go with this issue? Is it a bit of fundamental feature to fix? Thanks

hanwesh avatar Feb 19 '19 22:02 hanwesh