Azure App Service WebApp Graceful shutdown/Restart
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have created an ASP.Net Core 2.1 WebApp that has a single HostedService to run a background process, the process can take up to 20 seconds to complete once a cancelation token has been cancelled. This all works fine locally when run on IIS Express - the StopAsync() method is called when the IIS Express site is stopped and waits for the process to complete before the application is terminated.
When I run this app in an Azure App Service it does not shutdown or restart gracefully the StopAsync() is called but the application is killed within a few seconds not allowing the application to shutdown gracefully.
I have tried adding the following in web.config:
<aspNetCore shutdownTimeLimit="90" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".logsstdout">
And the following in Program.cs but this had no effect:
public static IWebHostBuilder CreateWebHostBuilder(string args) =>
WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.UseShutdownTimeout(TimeSpan.FromSeconds(90));
Are there any other settings I need to set in an Azure App Service to increase the Shutdown timeout?
Many thanks.
azure asp.net-core azure-web-sites
add a comment |
I have created an ASP.Net Core 2.1 WebApp that has a single HostedService to run a background process, the process can take up to 20 seconds to complete once a cancelation token has been cancelled. This all works fine locally when run on IIS Express - the StopAsync() method is called when the IIS Express site is stopped and waits for the process to complete before the application is terminated.
When I run this app in an Azure App Service it does not shutdown or restart gracefully the StopAsync() is called but the application is killed within a few seconds not allowing the application to shutdown gracefully.
I have tried adding the following in web.config:
<aspNetCore shutdownTimeLimit="90" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".logsstdout">
And the following in Program.cs but this had no effect:
public static IWebHostBuilder CreateWebHostBuilder(string args) =>
WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.UseShutdownTimeout(TimeSpan.FromSeconds(90));
Are there any other settings I need to set in an Azure App Service to increase the Shutdown timeout?
Many thanks.
azure asp.net-core azure-web-sites
add a comment |
I have created an ASP.Net Core 2.1 WebApp that has a single HostedService to run a background process, the process can take up to 20 seconds to complete once a cancelation token has been cancelled. This all works fine locally when run on IIS Express - the StopAsync() method is called when the IIS Express site is stopped and waits for the process to complete before the application is terminated.
When I run this app in an Azure App Service it does not shutdown or restart gracefully the StopAsync() is called but the application is killed within a few seconds not allowing the application to shutdown gracefully.
I have tried adding the following in web.config:
<aspNetCore shutdownTimeLimit="90" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".logsstdout">
And the following in Program.cs but this had no effect:
public static IWebHostBuilder CreateWebHostBuilder(string args) =>
WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.UseShutdownTimeout(TimeSpan.FromSeconds(90));
Are there any other settings I need to set in an Azure App Service to increase the Shutdown timeout?
Many thanks.
azure asp.net-core azure-web-sites
I have created an ASP.Net Core 2.1 WebApp that has a single HostedService to run a background process, the process can take up to 20 seconds to complete once a cancelation token has been cancelled. This all works fine locally when run on IIS Express - the StopAsync() method is called when the IIS Express site is stopped and waits for the process to complete before the application is terminated.
When I run this app in an Azure App Service it does not shutdown or restart gracefully the StopAsync() is called but the application is killed within a few seconds not allowing the application to shutdown gracefully.
I have tried adding the following in web.config:
<aspNetCore shutdownTimeLimit="90" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".logsstdout">
And the following in Program.cs but this had no effect:
public static IWebHostBuilder CreateWebHostBuilder(string args) =>
WebHost.CreateDefaultBuilder(args)
.UseStartup<Startup>()
.UseShutdownTimeout(TimeSpan.FromSeconds(90));
Are there any other settings I need to set in an Azure App Service to increase the Shutdown timeout?
Many thanks.
azure asp.net-core azure-web-sites
azure asp.net-core azure-web-sites
asked Nov 15 '18 at 17:19
Brett RogersBrett Rogers
162
162
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If we want to gracefully shut down the webapp, we could inject IApplicationLifetime and use the property ApplicationStopping in the Startup.cs
IApplicationLifetime is a new interface in ASP.NET Core under the Microsoft.AspNetCore.Hosting namespace. The interface is designed to give a developer the opportunity to gracefully startup but mostly shutdown the application.
Demo code
public void Configure(IApplicationBuilder app, IHostingEnvironment env,IApplicationLifetime applicationLifetime)
...
applicationLifetime.ApplicationStopping.Register(OnShutdown);
...
private void OnShutdown()
//todo
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324802%2fazure-app-service-webapp-graceful-shutdown-restart%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If we want to gracefully shut down the webapp, we could inject IApplicationLifetime and use the property ApplicationStopping in the Startup.cs
IApplicationLifetime is a new interface in ASP.NET Core under the Microsoft.AspNetCore.Hosting namespace. The interface is designed to give a developer the opportunity to gracefully startup but mostly shutdown the application.
Demo code
public void Configure(IApplicationBuilder app, IHostingEnvironment env,IApplicationLifetime applicationLifetime)
...
applicationLifetime.ApplicationStopping.Register(OnShutdown);
...
private void OnShutdown()
//todo
add a comment |
If we want to gracefully shut down the webapp, we could inject IApplicationLifetime and use the property ApplicationStopping in the Startup.cs
IApplicationLifetime is a new interface in ASP.NET Core under the Microsoft.AspNetCore.Hosting namespace. The interface is designed to give a developer the opportunity to gracefully startup but mostly shutdown the application.
Demo code
public void Configure(IApplicationBuilder app, IHostingEnvironment env,IApplicationLifetime applicationLifetime)
...
applicationLifetime.ApplicationStopping.Register(OnShutdown);
...
private void OnShutdown()
//todo
add a comment |
If we want to gracefully shut down the webapp, we could inject IApplicationLifetime and use the property ApplicationStopping in the Startup.cs
IApplicationLifetime is a new interface in ASP.NET Core under the Microsoft.AspNetCore.Hosting namespace. The interface is designed to give a developer the opportunity to gracefully startup but mostly shutdown the application.
Demo code
public void Configure(IApplicationBuilder app, IHostingEnvironment env,IApplicationLifetime applicationLifetime)
...
applicationLifetime.ApplicationStopping.Register(OnShutdown);
...
private void OnShutdown()
//todo
If we want to gracefully shut down the webapp, we could inject IApplicationLifetime and use the property ApplicationStopping in the Startup.cs
IApplicationLifetime is a new interface in ASP.NET Core under the Microsoft.AspNetCore.Hosting namespace. The interface is designed to give a developer the opportunity to gracefully startup but mostly shutdown the application.
Demo code
public void Configure(IApplicationBuilder app, IHostingEnvironment env,IApplicationLifetime applicationLifetime)
...
applicationLifetime.ApplicationStopping.Register(OnShutdown);
...
private void OnShutdown()
//todo
answered Nov 16 '18 at 1:37
Tom SunTom Sun
17.9k2923
17.9k2923
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53324802%2fazure-app-service-webapp-graceful-shutdown-restart%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown