Thread in Global.asax does not work after publishing the web site

Question

I am developing a web application where I have implemented job scheduler using Global.asax. I have used thread to start the job for particular duration.

It works fine if I run the application through visual studio. But when I publish and deploy it to the server the thread doesn't work.

Please help me to resolve this issue. Is there any alternative for this.

Please find the sample code below,

protected void Application_Start()
    {
        Thread thread = new Thread(new ThreadStart(ThreadFunc));
        thread.IsBackground = true;
        thread.Name = "ThreadFunc";
        thread.Start();
    }

    protected void ThreadFunc()
    {
        System.Timers.Timer t = new System.Timers.Timer();
        t.Elapsed += new System.Timers.ElapsedEventHandler(TimerWorker);
        t.Interval = 10000;
        t.Enabled = true;
        t.AutoReset = true;
        t.Start();
    }

    protected void TimerWorker(object sender, System.Timers.ElapsedEventArgs e)
    {
        //work args
    }

Thanks,

Vijay

seems good. may be IIS Issue?? why cant u use Services, instead of threads?? as @MK. anwserd in his link . — Ravi Gadag, Jan 20 '12 at 16:37

score 0 · Accepted Answer · edited May 23 '17 at 10:24

0

I don't think spawning a thread in global.asax is a good idea. Please see this question for better solutions.

edited May 23 '17 at 10:24

Community

1
1

answered Jan 20 '12 at 16:07

MK.

33,605
18
74
111

Now I have written a windows service to perform scheduler job. – VJOY Jan 23 '12 at 07:14

score 0 · Answer 2 · answered Jan 20 '12 at 16:32

0

If there is no activity on your site for a period of time, it is shut down automatically.

To circumvent this, google "Keep asp.net site alive"

But you'll find a bunch of duct-tape like hacks. I would change the architecture.

answered Jan 20 '12 at 16:32

Steve Wellens

20,506
2
28
69

Thread in Global.asax does not work after publishing the web site

2 Answers2