Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Scheduler in Timer Mode kills portalScheduler in Timer Mode kills portal
Previous
 
Next
New Post
10/13/2008 7:20 AM
 

The more the merrier Rodney :)

I've just now gone ahead with Alex' suggestion and have installed 4.90 on the same box. I did set up a fresh 4.8x in the past for the same purpose and I'm positive it also hung on restart after changing to timer method. However, this time 4.90 started up fine after the switch.

So then I tried settting all config settings in my main portal to match the fresh instance. I was using settings pretty much identical to Rodney's further up. Then I also went into web.config and commented out three third party httphandlers just in case they had anything to do with it.

The portal got hung up on restart the same as it always has.

What I'd really like to know is what "Timer Method" actually does so differently from "Request Method" so that I might be able to take a guess at what sort of module might be affecting this.

Any advice is appreciated.

Rob

 
New Post
10/13/2008 9:21 AM
 

FYI Essentially the timer method creates new threads to process threads and the request method evaluates if a task needs to be down when someone (anyone will do) is browsing the website.  The request method was added after people reported that scheduled methods sometimes didn't work - this was quite some time ago, and I think may have been related to hosting providers locking down/limiting what a shared hosting account can do. Whenever the application pool is unloaded, all related threads are supposed to be garbage collected by the .net framework, but i've seen reports of multiple threads performing the same scheduled tasks, so i'm not convinced asp.net does an effective job in this case and I've always used request mode. The primary disadvantage of the request mode is that tasks may not execute on time if you have a low traffic site.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/26/2008 10:58 AM
 

What are the options for this value in the db?  I switched this to '0' from '1' but cant get the site back.  Help.

ROBAX wrote
 

 Mitch Sellers wrote
 

 

This is very odd, what happens when you try to navigate to the site?

I have at least 20 installations of 4.8.4 running with the scheduler in Timer Mode without issue.

 

After switching mode, the site works until it is restarted - it appears to get partway through restarting and then hangs on something. The only way out for me has been to switch back again in the db. No exceptions are recorded when this happens. I guess there's a chance that something might would eventually time out, but I've only let it sit for about 20 mins because it's supposed to be a live system.

Rob

 
New Post
10/26/2008 2:26 PM
 

The db values are:

0=disabled

1=timer method

2= request method

 

joiseystud wrote
 

What are the options for this value in the db?  I switched this to '0' from '1' but cant get the site back.  Help.

 ROBAX wrote
 

 

 Mitch Sellers wrote
 

 

This is very odd, what happens when you try to navigate to the site?

I have at least 20 installations of 4.8.4 running with the scheduler in Timer Mode without issue.

 

After switching mode, the site works until it is restarted - it appears to get partway through restarting and then hangs on something. The only way out for me has been to switch back again in the db. No exceptions are recorded when this happens. I guess there's a chance that something might would eventually time out, but I've only let it sit for about 20 mins because it's supposed to be a live system.

Rob

 

 
New Post
10/27/2008 4:19 PM
 

Ok.  Good news.  By some miracle I was able to get my site working in timer moder which fixed all scheduler issues.  I think the issue may have been that I had tons of stuff stuck in the Queue so when going into timer mode it would hang.  In order to clear the queues in request mode I had to turn the particular schedule item on and off until it stopped sending emails (about 12 emails came out of the queue after 4 restarts of the schedule item).  Once the queue was clear the site accepted timer mode and went off like a rocket.  Now my usersonline works perfect and the emails go every time within a minute. 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Scheduler in Timer Mode kills portalScheduler in Timer Mode kills portal


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out