Hi all,

I've been chasing some issues with the scheduler and have a question. Background: I've recently implemented a module which runs a scheduled task that takes a looooong while to complete. I run it infrequently, but noticed that whilst it was running no other scheduled tasks ran. Odd, I thought, doesn't this thing multi-thread? I found this design doc (a bit old) that does specify a multi-threading scheduler:

http://www.dotnetnuke.com/LinkClick.aspx?fileticket=Sa3oPZCNyw0%3D&tabid=478&mid=857

Investigating, I found that in all the web.configs I have going back to version 3.1 the maxThreads setting is "1", not "-1" as described. In other words, only one scheduler thread allowed. Which explains what's happening on my site!  :)

Now I doubt  this is just a typo in web.config that no-one has noticed in all this time, so I wonder if there's some history here and a  very good reason why we don't multi-thread the scheduler. Can anyone comment on this before I take a deep breath and set the maxThreads in my web.config to a higher value ? And also on whether it would be best to just set maxThreads="2" or go back to the original design and set it to "-1"?

Thanks In Advance,

Graham

Graham, what did you discover here? Anyone else have a comment on this?

be aware, that DNN scheduler is not ideal for long lasting threads, due to web sites might get unloaded after inactivity or consumption of resources. If you need reliable scheduled services, you should consider implemeting it using windows scheduler or SQL Server.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN