C# - Quartz scheduler stopped running when no activity on the site

Question

I have created asp.net site with quartz scheduler. The job is running in background and there is no other activity on the site.

Quartz scheduler scheduled for every 30 minutes.

After IIS started, Scheduler is running correctly.

But after some time, Scheduler stopped running (about 1 hour).

If have one or more activity on site as user login or view dashboard then Scheduler runs correctly.

But when have no activity on site it stops running.

How to keep alive my Scheduler for all the times when no activity on site?

P/s: I know my question can be duplicate with other question. But i still ask because i can not comment to ask in answers of other question.

Edit:

Day Running at: 7/14/2016 4:00:00 AM
--
Day Running at: 7/14/2016 4:30:00 AM
--
Day Running at: 7/14/2016 5:00:00 AM
--
Stopped running
--
Day Running at: 7/14/2016 2:00:00 PM
--
Day Running at: 7/14/2016 2:30:00 PM
--
Day Running at: 7/14/2016 3:00:00 PM
--
Stopped running
--

felix-b · Accepted Answer · 2016-07-14T09:51:39.250

8

By default, IIS will unload your application if the application receives no requests for a period of time.

You can configure IIS to never unload your application.There are plenty of reasons IIS will unload your application - make sure you disable all of them. It is in the application pool settings, better go to Advanced Settings and pass carefully through all of them.

On a side note, if you have a background job you need to reliably run on schedule, why not deploy it in a Windows service, in addition to the web application? Web applications are best at serving incoming requests, not running scheduled jobs.

UPDATE

Check out these in Advanced Settings of your application pool:

Process Model / Idle Time-out and Idle Time-out Action
Recycling / Regular Time Interval, Request Limit, Private Memory Limit, Virtual memory Limit

edited Jul 14 '16 at 09:51

answered Jul 14 '16 at 09:23

felix-b

8,178
1
26
36

I have some reasons to use background job in web application. I tried setting increase Session Timeout Idle but my job still stopped running. So, can you suggest for me some reasons IIS will unload my application? – TonyBui Jul 14 '16 at 09:33
@TonyBui : shared hosting? :) – Andrei Rînea Jul 14 '16 at 09:33
@AndreiRînea: No, i host my web application in private hosting. – TonyBui Jul 14 '16 at 09:36
By default IIS will unload an AppPool if it hasn't received any request for 20 minutes (1200 seconds). – Andrei Rînea Jul 14 '16 at 09:44
@TonyBui, please see update in the answer, with specific settings you may need to change. – felix-b Jul 14 '16 at 09:52
1

@AndreiRînea: 20 minutes is in Advanced Settings/Idle Time-out? – TonyBui Jul 14 '16 at 09:55
@TonyBui - yes, it is – felix-b Jul 14 '16 at 09:57
@TonyBui : yup, that's the one. – Andrei Rînea Jul 14 '16 at 09:58

Andrei Rînea · Answer 2 · 2016-07-14T09:48:12.197

Normally you shouldn't use ASP.NET for recurring tasks because it is not built for that, it's recommended to use a Windows Service for that.

However, you could use WebBackgrounder. Scott Hanselman seems to endorse it ;) He also demonstrates how to use Quartz.NET along with it.

Or you could start a thread that generates requests from your app into itself each minute, to keep it up:

    protected void Application_Start()
    {
        // ...

        ThreadPool.QueueUserWorkItem(o => PingMyself());
    }

    private static void PingMyself()
    {
        var webClient = new WebClient();
        while (true)
        {
            Thread.Sleep(TimeSpan.FromMinutes(1));
            webClient.DownloadString("http://my.public.address.com");
        }
    }

Quartz.NET Also stop tasks, if our appPool stop. and AppPool will stop when nobody will hit webApp for long time. — Keval Patel, Jul 12 '23 at 04:56

C# - Quartz scheduler stopped running when no activity on the site

2 Answers2

Linked