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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Module Caching does not seem to be working since 4.9.0 UpgradeModule Caching does not seem to be working since 4.9.0 Upgrade
Previous
 
Next
New Post
10/12/2008 8:26 AM
 

 Hey Rodney,

I agree with you.  I can't quite work it out, but something is definately off with the new caching code.  I've noticed it in our own sites as well as with problems on DotNetNuke.com

 

 
New Post
10/12/2008 4:01 PM
 

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
10/12/2008 4:31 PM
 

I just noticed the Schedule Status page (didn't even know about this!) - I am not sure this is healty:

The UsersOnline is 2400 seconds overdue even though it says it completed successfully. The time remaining on those top 3 tasks are suspiciously similar...

 

Current Status: WAITING_FOR_REQUEST
Max Threads: 1
Active Threads: 0
Free Treads: 1
Command: Start    Stop



Items in Queue
Schedule ID Type Next Start Overdue
(seconds)
Time Remaining
(seconds)
Object Dependencies Triggered By Servers
5 DotNetNuke.Services.Log.EventLog.SendLogNotifications, DOTNETNUKE 10/12/2008 4:43:52 PM   4277.7876697 EventLog STARTED_FROM_BEGIN_REQUEST  
7 DotNetNuke.Modules.Admin.ResourceInstaller.InstallResources, DOTNETNUKE 10/12/2008 4:43:52 PM   4277.7876697 ResourceInstaller STARTED_FROM_BEGIN_REQUEST  
16 DotNetNuke.Modules.Forum.CleanupEmailQueuedTasks, DotNetNuke.Modules.Forum 10/12/2008 4:43:52 PM   4277.7876697   STARTED_FROM_BEGIN_REQUEST  
2 DotNetNuke.Services.Log.SiteLog.PurgeSiteLog, DOTNETNUKE 10/12/2008 6:32:31 PM   10795.8812175 SiteLog STARTED_FROM_BEGIN_REQUEST  
4 DotNetNuke.Services.Log.EventLog.PurgeLogBuffer, DOTNETNUKE 10/12/2008 6:32:31 PM   10795.8812175 EventLog STARTED_FROM_BEGIN_REQUEST  
3 DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE 10/13/2008 6:32:31 PM   97195.8812175 ScheduleHistory STARTED_FROM_BEGIN_REQUEST  
6 DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE 10/12/2008 6:32:31 PM   10795.8812175 SearchEngine STARTED_FROM_BEGIN_REQUEST  
17 BizModules.UltraPhotoGallery.Scheduling.AutoSyncScheduler, BizModules.UltraPhotoGallery 10/12/2008 8:36:12 PM   18216.9698715 UltraMediaGallery STARTED_FROM_BEGIN_REQUEST  
15 DotNetNuke.Modules.Forum.StartEmailQueuedTasks, DotNetNuke.Modules.Forum 10/12/2008 3:06:12 PM 1583.0301285 0   STARTED_FROM_BEGIN_REQUEST  
12 DotNetNuke.Services.Cache.PurgeCache, DOTNETNUKE 10/12/2008 2:56:12 PM 2183.0301285 0   STARTED_FROM_BEGIN_REQUEST  
1 DotNetNuke.Entities.Users.PurgeUsersOnline, DotNetNuke 10/12/2008 2:51:12 PM 2483.0301285 0 UsersOnline STARTED_FROM_BEGIN_REQUEST  
18 Dataspring.DNN.Modules.OptInAdvanceEmail.SendNewsletters,Dataspring.DNN.Modules.OptInAdvanceEmail 10/12/2008 2:51:56 PM 2438.356824 0   STARTED_FROM_BEGIN_REQUEST  

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
10/27/2008 6:51 PM
 

Some information on how to read this table:

Time Remaining - this is the number of seconds before a scheduled job is expected to run again ( ie. it is the Next Start - Current Date/Time )

OverDue - this is the number of seconds that a job has been waiting to execute once it has been triggered to run. Please note that if multiple jobs are scheduled to execute at, or near, the same time, only 1 thread is spawned ( this is configurable ) and the jobs are executed in series. If one of the jobs takes an exceptionally long time to complete - the other jobs may be waiting ( and overdue ) for quite some time.

STARTED_FROM_BEGIN_REQUEST - this means that you are using Request mode rather than Timer mode. In Request mode, it means that if your site is not getting much traffic, the scheduled jobs will not trigger on their expected schedule and you may end up with many overdue jobs executing ( and you will likely see many jobs with the same Next Start date/time ).

With all the configuration options available in the Scheduler, it is next to impossible to solve these types of issues through Forum posts. It really requires direct access to the system to perform analysis and diagnosis in the operating environment. This is what we do through our Support offering, and we have helped many users to optimize their scheduled jobs in the past.

I hope the information I have provided has been helpful...


My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
10/28/2008 11:15 AM
 

Shaun,

I appreciate the reply with the additional information, and it is useful to some extent.  However, the latest documentation on the scheduler is given in the downloads section is labeled:  DotNetNuke 4.9.0, and it actually contains documentation from a zip version Docs v4.1.1. The doc included for the Scheduler is Version 1.0.0 Last Updated: November 28, 2005. This particular document is out-of-date with what is being delivered and setup by default.   In my case, I found the defaults to be different, and I had to change them to get the scheduler to fire.  By default v04.09.09 has the web config maxThreads set to '1', and there is no setting for the 'enabled' setting.  When this setup is used my events never fired correctly even after an application restart. and the 'Start' 'Stop' command links were greyed out.  I tried using the maxThreads='-1' but it never worked. I changed the maxThreads to '10', and added the enabled='true' setting, and after restarting the application events started firing.

It would really be useful to have whoever is doing the caching code reply to this thread to document the changes that Sebastian mentions.  It may help developers understand the issues more fully.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Module Caching does not seem to be working since 4.9.0 UpgradeModule Caching does not seem to be working since 4.9.0 Upgrade


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