Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

$4.95 Windows Hosting at Webhost4life.com
  Ads  
Engage Software - Training Partner for DotNetNuke
 


  Sponsors  

Meet Our Sponsors

Portal Webhosting - Hosting For Developers
Red-Gate Software
MaximumASP
SourceGear - Tools for Developers
.: CounterSoft :.
telerik
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Configure It! (...  Scheduler dead as a Dodo! 4.90
Previous Previous
 
Next Next
New Post 12/3/2008 6:32 AM
User is offline Jon Seeley
499 posts
www.seeleyware.com
8th Ranked


Re: Scheduler dead as a Dodo! 4.90 

Well this is disappointing to hear (but glad it has at least received some attention now).  As of 4.9 my scheduler has pretty much ceased to exist as well.

All of my custom tasks (which I have full control over and can "log" to watch what is happening) were emailing me TONS of errors -- basically thread aborting.  On the same token, they were trying to fire off as many as 5 times each (and these are all reminder services, BTW, so the few reminders that actually sent before it crashed would send mulitple times, doh!).  I ended up creating webservices to expose the functionality I needed and wrote Windows services to run the reminders instead.  That solved it.

Bringing that up... I actually talked with Joe Brinkman about this at OpenForce a few weeks ago and his response really wasn't comforting.  I asked the question in relation to the "Professional" version that will be coming out soon... basically asked that if I had professional and something like this occurred what would they do.  In shortened form he told me they'd identify the module that was causing the issue (which I know to not be the case, it is the core) and then I could take the steps to fix it.  I'm sure the actual response will be different when the professional version is out and fully supported, but that didn't really give me warm fuzzies.  He also confirmed that the "best" solution for somebody with full control over their portal is to indeed use Windows services to foot the requests and offload it from the portal (makes sense, but doesn't help if you don't have control over the module--ie., core or 3rd party).

As with Rob, Timer mode completely kills my entire portal altogether even if I disable virtually all the tasks (I sat down one day and selectively turned them on one by one -- core only and then my own -- and watched it kill the portal each time).  Request mode worked better in previous versions as in it actually worked at all, but now with 4.9 it is pretty much dead in the water.  Thank goodness I have full control over everything and can write Windows services to handle my tasks.

I very much look forward to a solution but in the meantime will just continue writing Windows services to handle all the new tasks I come up with.


-- Jon Seeley
http://www.seeleyware.com
 
New Post 12/3/2008 6:35 AM
User is offline Jon Seeley
499 posts
www.seeleyware.com
8th Ranked


Re: Scheduler dead as a Dodo! 4.90 

 Will Morgenweck wrote

Rob,

Out of curiousity, is your scheduler set to Request or Timer mode?  I have heard of few people locking up their sites when they switch scheduler, but I think that could be due to all the overdue tasks.  Timer mode seems to work well for us.  If you are running request mode then you can try the following:

1) Go to the sql menu and run "truncate table {databaseOwner}{objectQualifier}schedulehistory"

2) Go to host settings and change the scheduler mode to timer.

3) Click Update, then Restart Application.

 

If you are already in timer mode, then still truncate the schedulehistory table then restart the application.  This will usually get the scheduler running properly again.

Thought I'd chime in on this part to.  I completely nuked my schedule history each time I tried switching (see my previous post on this thread) and it continued to lock up my entire portal.  I actually had to manually switch back to request mode through the database itself because the portal was completely dead.  My first version of DNN was 4.0 and I've been following the upgrades ever since (typically what I considered "major" upgrades so I haven't been on board with each upgrade since the initial 4.0 release).


-- Jon Seeley
http://www.seeleyware.com
 
New Post 12/3/2008 10:06 AM
User is offline Alex Shirley
2481 posts
5th Ranked




Re: Scheduler dead as a Dodo! 4.90 
Modified By Alex Shirley  on 12/3/2008 1:10:41 PM)

All the related Gemini issues are resolved for 4.9.1. No release date at this time, it is unlikely to happen this week or next (just a hunch, sorry). The gemini issues however were never on a backburner, and they were diagnosed and treated within 5 days of logging within Gemini (2 days of which was a weekend).

Thanks...


Well might as well promo one of my DNN sites as I'm here: http://www.snasty.co.uk
 
New Post 12/3/2008 10:29 AM
User is offline Jon Seeley
499 posts
www.seeleyware.com
8th Ranked


Re: Scheduler dead as a Dodo! 4.90 

 Alex Shirley wrote

All the related Gemini issues are resolved for 4.9.1. No release date at this time, it is unlikely to happen this week or next (just a hunch, sorry). The gemini issues however were never on a backburner, and they were diagnosed and treated within 5 days of logging within Gemini (2 days of which was a weekend).

Thanks...

Noice!  If you need a tester on it I'd be happy to test it (make a copy of my environment and run on a staging server).


-- Jon Seeley
http://www.seeleyware.com
 
New Post 12/3/2008 8:18 PM
User is offline ROBAX
1885 posts
5th Ranked


Re: Scheduler dead as a Dodo! 4.90 

 Alex Shirley wrote
 

All the related Gemini issues are resolved for 4.9.1. No release date at this time, it is unlikely to happen this week or next (just a hunch, sorry). The gemini issues however were never on a backburner, and they were diagnosed and treated within 5 days of logging within Gemini (2 days of which was a weekend).

Ok yep I can see now where Charles says the cache issue fixes the scheduler problem - hurrah! Let's get his one out asap :))) It's a real killer.

 
Previous Previous
 
Next Next
  Forum  General DotNetN...  Configure It! (...  Scheduler dead as a Dodo! 4.90
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


OnyakTech
Modules for Help Desks, Live Chat, Project Management, CRM, Charting, Reporting, Scrolling Text/Images, Portal Community tools and much more.
www.OnyakTech.com
IHostASP.NET Provides the Ideal DNN Hosting
We will help you with the installation, configuration, and troubleshooting of your DNN portal, no task is too big or small for us. Unlike other companies we are not just providing a reliable hosting service, but we are also focused on providing the best DotNetNuke hosting service on the internet.
www.ihostasp.net
$7.16/mo - Powerful DotNetNuke / DNN Hosting
Powerful DotNetNuke / DNN Hosting on Windows 2008 and 2003 servers, starting at under $8/mo with FREE SQL 2008 on certain plans and FREE SQL 2005 on all plans with FREE Installation and expert support.
www.re-invent.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP