IApplicationLifetime ApplicationStopped events not getting called when stopping/restarting Azure web app

[rogerdawson]

We've noticed the ApplicationStopped event doesn't seem to get called if you stop or restart a dotnetcore Azure web app (full fat .net 4.6 framework).

Stopping our site in IIS Express doesn't work either (using the system tray stop site option) although the Kestrel server does appear to work (assuming you stop it using ctrl+c).

We did come across the ApplicationStopping issue (#812) which is why we are using ApplicationStopped but it doesn't seem to work. Would I be correct in assuming that selecting stop or restart from the Azure portal is not considered a graceful shutdown?

[muratg]

@rogerdawson Could you provide a simple repro app?

@JunTaoLuo can give it a try.

[rogerdawson]

Hello, I haven't got anything to hand as its embedded in our main app. I'm guessing a standard RTM web app will reproduce the error but the problem will be you'll need a database to log messages to or some other means by which you can detect if the shutdown method has been called. If you haven't got anything like that to hand then I guess I could try and create something. Let me know how you would prefer to proceed. Many Thanks, Roger

[muratg]

@rogerdawson it would be great if you could share a simple repro app on github for us to investigate. Thanks!

[tx8821]

As said by OP, none of the shutdown events actually fire, when using IIS Express. During debugging with Visual Studio, neither clicking on "Stop Debugging" button in VS, nor right-clicking IIS Express icon in tray and choosing Stop Site/Exit, trigger the event. These thing is just not working! And who runs Kestrel in a console?!...

[rogerdawson]

Hi,

I'm a bit snowed under at the moment so I can't produce anything
immediately (we can live with the problem for now but I'm registering the
fact there is a bug/issue). As the latest comment states, a console app is
a non-starter so the only way for me to reproduce would be to re-create a
web app that logs to a database or app insights but none of the publish
settings will be relevant as you'll need to publish your own Azure account.
Running a default web app project in IIS Express and breaking pointing the
shutdown event should be all you need to replicate in IIS Express though.

Thanks,

Roger

On 8 September 2016 at 21:58, Murat Girgin notifications@github.com wrote:

@rogerdawson https://github.com/RogerDawson it would be great if you
could share a simple repro app on github for us to investigate. Thanks!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#846 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABWODUIcsR5GUxUuPN5ZSE_RBDkM08LKks5qoHcGgaJpZM4Jxsey
.

Roger Dawson

GA Digital Ltd

T: +44 (0)1202 619102 <%2B44%20%280%291425%20270970> M: +44
(0)7816 825858 <%2B44%20%280%297885%20957239> F: +44 (0) 808 280
0358

_W: _www.ga-inst.co.uk http://www.ga-inst.co.uk/\ E:
roger.dawson@ga-digital.com graham.cheale@ga-digital.com

This e-mail and any attachment is intended for the named addressee(s) only,
or person authorised to receive it on their behalf. The content may be
privileged and should be treated as confidential and the recipient may not
disclose this message or any attachment to anyone else without
authorisation. Unauthorised use, copying or disclosure may be unlawful. If
this transmission is received in error please notify the sender immediately
and delete this message from your e-mail system. Any view expressed by the
sender of this message or any attachment may be personal and may not
represent the view held by GA Digital Ltd. All electronic transmissions to
and from GA Digital Ltd are recorded, may be monitored and are scanned for
viruses and content. Whilst we maintain virus checks on inbound e-mails we
accept no liability for viruses or other material introduced with this
message.

GA Digital Ltd is registered in England under registered number 06530309
whose registered office address is at Beacon House, 15 Christchurch Rd,
Bournemouth, Dorset, BH1 3LB. VAT Registration Number: GB 929 6678 60.

[guardrex]

@rogerdawson As a workaround (or substitute) did you have any luck trying a subscription to Unloading/ProcessExit?

https://github.com/dotnet/corefx/issues/10012#issuecomment-232436326

[rogerdawson]

Hi @guardrex , no, I haven't tried that. We've bailed from running our back-end service as a web app as it's just too unreliable - we've had no end of problems with intermittent restarts or the app services (see WEBSITE_LOCAL_CACHE_OPTION for instance which is necessary due to Azure network storage 'glitches'). Web jobs wasn't any better to be honest. We are running as service on a VM now and as well as better reliability we have found performance is almost twice as good (running on a 2-core D2_V2) as opposed to our service plan which was a 4-core S3. Our system is mostly IO bound so we guess this is down to networking. The service is still running as a web app but we now get clean shutdowns (same code, but Windows obviously shuts the service down gracefully so it must be Azure that isn't shutting down the web app gracefully). Thanks for the advice though.

[tomazv]

I'm having the same problem.

Here's a repro app: https://github.com/tomazv/applifetime

It writes events to a log and displays the log on each request. It only logs "Application started" and "Before run" but no other events when stopping or restaring the site on Azure.