Kestrelhttpserver: about pool recycling process.

[netcore-jroger]

I have such a problem.
when wu use IIS, It will automatically recycle the application pool from time to time should。now we use KestrelHttpServer will have this problem ?
Now it is actually a console application, so we should not have this problem. Am I right ?

[davidfowl]

If you us Kestrel behind IIS, IIS will manage the process like it always did. It'll restart the process from time to time and that will restart your application (which has kestrel loaded). If you use kestrel by itself then nothing will restart.

[netcore-jroger]

@davidfowl Thanks for your answer! With my thoughts as.

[clement911]

Are you saying that IIS will restart both the iis process AND the .net core process?

[davidfowl]

Yes. IIS signals to the module, the module signals to the .NET Core process

[clement911]

I see. Thanks.

[hslosangeles]

Hey Guys,

so I just came across an issue on our core deployment. Our site died unexpected a few times until I figured out it was always right after an IIS Reset every 29 hours (the regular iis app-pool recycle time). It looks like on recycle it literally kills kestrel and even an IIS restart doesn't help. Only a full server restart brings it back to life. Any ideas?? Can I actually set the the app-pool to not recycle while running a core app? Or is it still necessary??

Thank for your help!

[davidfowl]

@Cal279 are you saying that a server restart is required to make new requests work? I'm not aware of that problem. When a new request comes in it should just start a new process and things should work.