Home/ Questions/Q 52839
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T16:58:11+00:00

Consider this code… using System.Threading; //… Timer someWork = new Timer( delegate(object state) {

  • 0

Consider this code…

using System.Threading; //... Timer someWork = new Timer(     delegate(object state) {         //Do some work here...     },     null, 0, 60000);  HttpContext.Current.Application['SomeWorkItem'] = someWork;

Could this be dangerous? Caching a timer in the Application to perform some work in the background while your site runs seems safe, but I wondered if anyone has some experience with this.

I’m sure that writing a Service to run in the background would certainly be much better, but sometimes that isn’t always an option. Is this an alternative?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. This would generally be a bad idea, as System.Threading.Timer uses threads from the ThreadPool, the same as ASP.Net.

    If for what ever reason your timer delegate blocks or stops, the timer will simply begin a new Thread after the timeout period, which eats in to the Threads available for ASP.net.

    If they all begin blocking, effectively you will not be able to serve any more web requests (probably a bad thing)

    • 0