Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsOther Extension...Other Extension...Scheduler behind the scenesScheduler behind the scenes
Previous
 
Next
New Post
2/22/2014 12:58 PM
 

Hi Everybody,

Is there any documentation of how the scheduler works exactly? My problem is that it seems to fire more than one of my custom schedulers at once. Does anybody if that could be the case?


Cheers,
Nils

 
New Post
2/23/2014 4:51 AM
 
The scheduler runs frequently, either triggered by each page call or as a background long running thread and checks for all the jobs to be executed. if next execution time has occurred, the job will be executed and after completion next execution time written to the database. Regarding multiple instances of the same job running the same time, there used to be issues in previous versions, which should be solved meanwhile, though it is still best practice, configuring jobs not running too frequent (depending on estimated execution time).

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/23/2014 2:18 PM
 

Hi Sebastian,

Thank you very much for the answer. What issues have that been? I am running on version 7.2.1 (with a minor patch as per this thread), I assume the issues have been fixed in this version. Is it correct that the scheduler will fire up a thread for each scheduler event that has to be executed? If yes is there a way to avoid this?

What is "too frequent" and why is it best pactice?

I am running 5 custom schedulers. Each takes up to 2 / 2.5 minutes to run (they include a call to a web service to receive data). They are executed every 20 minutes (which I assume is quite often).

 

Cheers,
Nils

 
New Post
2/24/2014 5:12 AM
 
FWIW - if you have scheduled events that are critical to each other or need to be triggered in a specific order - then you may need to consider running them all inside a single dnn scheduler event = and manage the actual action timing inside that event.

Doing this will let you much more granularly control how the events fire than what is offered by the dnn core event scheduler.

The scheduler system is much more loose than is suited to some scheduler needs ... in recent patches it has become more stable
- but there are still situations where - especially during a catchup phase that more than one scheduler task could fire at once.

Westa
 
New Post
2/25/2014 7:35 PM
 
Wes Tatters wrote:
[...] that more than one scheduler task could fire at once.

Westa

 

Hi Westa.

Thank you for your answer. 

Does that mean that DotNetNuke isn't able to control the started Threads properly? I set the "maxThreads" property in the web.config file to 1 (which is the default I believe). But it still seems to fire up more than one sometimes.

I can't merge all my Schedulers into one as they have to run independent from each other but I can't have more than one running at a time either. Is there anything that I can do to make sure that only one Scheduler-Thread runs at a time?

 

Cheers,
Nils

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsOther Extension...Other Extension...Scheduler behind the scenesScheduler behind the scenes


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out