1

After reading this :

http://www.mikesdotnetting.com/article/254/scheduled-tasks-in-asp-net-with-quartz-net

I was quite happy i could publish a web site that would do scheduled task on itself... Or that was i tought.

We did it, and it seems like IIS servers kill quartz just like any other scheduled task programmed inside web sites...

Am i right ?

Antoine Pelletier
  • 3,164
  • 3
  • 40
  • 62
  • 1
    You might have a look at my answer on **[What is causing my ASP.NET MVC app to stop emailing and recycling the app pool to immediately fix it?](https://stackoverflow.com/questions/36702817/what-is-causing-my-asp-net-mvc-app-to-stop-emailing-and-recycling-the-app-pool-t/36703584#36703584)**. Hope this helps... – Murat Yıldız May 15 '18 at 20:25
  • @MuratYıldız I added value to your answer, what about me ? I gave-up quartz and used an old task scheduler instead... But your answer is useful for futur users. – Antoine Pelletier May 16 '18 at 12:34
  • OK, thanks. Do not worry :) I also marked the question as useful. Regards... – Murat Yıldız May 16 '18 at 12:45

1 Answers1

4

Yes, you are right.

Basically - unless configured to do so, IIS will simply stop the application pool. Even if not, you put yourself into a corner for later growth.

The proper solution is to use an external scheduler (and possibly call a special URL to do the processing).

TomTom
  • 61,059
  • 10
  • 88
  • 148