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...Scheduler executing item concurrentlyScheduler executing item concurrently
Previous
 
Next
New Post
4/27/2009 4:25 PM
 

I am getting SQL Server deadlock errors appearing in my DNN event log, which I've tracked back to the SearchEngineScheduler item.  As I investigated, I have found that the scheduler is sometimes running multiple occurrences of the SearchEngineScheduler Item at the same time (up to 8 at a time).  I'm trying to figure out why the scheduler would do that.

I'm currently running DNN 4.8.2.  The scheduler is set to run in Timer mode.  The scheduled item is set to run once every 10 minutes, with no retry interval, and with no catchup.  After changing the settings on the scheduler and scheduler item, I restarted the IIS worker process to make sure that settings weren't being cached.

Here's a sample of the schedule history for this item.  In this case, everything ran successfully, but that is the exception rather than the rule:

Description Duration (seconds) Succeeded Start/End/Next Start
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
112.11 True S: 4/27/2009 3:38:35 PM
E: 4/27/2009 3:40:27 PM
N: 4/27/2009 3:48:35 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
113.72 True S: 4/27/2009 3:38:31 PM
E: 4/27/2009 3:40:24 PM
N: 4/27/2009 3:48:31 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
121.593 True S: 4/27/2009 3:38:29 PM
E: 4/27/2009 3:40:30 PM
N: 4/27/2009 3:48:29 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
118.126 True S: 4/27/2009 3:38:12 PM
E: 4/27/2009 3:40:10 PM
N: 4/27/2009 3:48:12 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
115.44 True S: 4/27/2009 3:37:56 PM
E: 4/27/2009 3:39:51 PM
N: 4/27/2009 3:47:56 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
108.75 True S: 4/27/2009 3:37:41 PM
E: 4/27/2009 3:39:29 PM
N: 4/27/2009 3:47:41 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
105.28 True S: 4/27/2009 3:37:25 PM
E: 4/27/2009 3:39:10 PM
N: 4/27/2009 3:47:25 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
109.643 True S: 4/27/2009 3:37:06 PM
E: 4/27/2009 3:38:56 PM
N: 4/27/2009 3:47:06 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
52.143 True S: 4/27/2009 3:36:50 PM
E: 4/27/2009 3:37:42 PM
N: 4/27/2009 3:46:50 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
40.267 True S: 4/27/2009 3:36:34 PM
E: 4/27/2009 3:37:14 PM
N: 4/27/2009 3:46:34 PM
DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE
Completed re-indexing content
32.563 True S: 4/27/2009 3:28:28 PM
E: 4/27/2009 3:29:00 PM
N: 4/27/2009 3:38:28 PM

Any thoughts on why the scheduler is running the SearchEngineSchedule multiple times concurrently?  If I can figure this out, I'm pretty sure the deadlock error will disappear.

Brad

 
New Post
4/28/2009 4:09 AM
 

 try to clear the search tables and re-index your site. 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/28/2009 10:44 AM
 

Thank you for your idea.  I ran this SQL, and the problem continues.  The next time the scheduler ran this job after I ran the script, it ran four instances of this job at the same time.  I expect that I will continue to have deadlock problems because the job is running multiple times.  Any other thoughts?

 
New Post
5/1/2009 11:37 AM
 

We're having the same problem with the scheduler running events multiple times.  We haven't been been able to pinpoint exactly where the problem is coming from.  We've tried various configs of the scheduler and it's the same problem.  We have 5 different scheduled tasks running and all of them from time to time will run 2 or more times.  The number of times they run seems random (although I'm sure it's not).  I've spent many hours trying to track down a solution to this problem and it has been reported on multiple threads but there appears to be no solution. Below is an example of the problem for purge users online but the problem is similar for all tasks.  Any help or direction is greatly appreciated.  Thanks

DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.733 True S: 5/1/2009 11:32:32 AM
E: 5/1/2009 11:32:32 AM
N: 5/1/2009 11:33:32 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.28 True S: 5/1/2009 11:31:30 AM
E: 5/1/2009 11:31:31 AM
N: 5/1/2009 11:32:30 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
2.533 True S: 5/1/2009 11:31:29 AM
E: 5/1/2009 11:31:32 AM
N: 5/1/2009 11:32:29 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.107 True S: 5/1/2009 11:30:28 AM
E: 5/1/2009 11:30:28 AM
N: 5/1/2009 11:31:28 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
1.156 True S: 5/1/2009 11:29:54 AM
E: 5/1/2009 11:29:55 AM
N: 5/1/2009 11:30:54 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.156 True S: 5/1/2009 11:28:53 AM
E: 5/1/2009 11:28:53 AM
N: 5/1/2009 11:29:53 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.05 True S: 5/1/2009 11:28:53 AM
E: 5/1/2009 11:28:53 AM
N: 5/1/2009 11:29:53 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.937 True S: 5/1/2009 11:28:42 AM
E: 5/1/2009 11:28:43 AM
N: 5/1/2009 11:29:42 AM
DotNetNuke.Entities.Users.PurgeUsersOnline, DOTNETNUKE
UsersOnline purge completed.
0.05 True S: 5/1/2009 11:27:40 AM
E: 5/1/2009 11:27:40 AM
N: 5/1/2009 11:28:40 AM

 
New Post
5/1/2009 11:51 AM
 

It sounds like you have Web Gardening enabled that spawns multiple ASP.NET processes for the same application.

I would ensure that in the IIS configuration that you do NOT have web gardening enabled!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Scheduler executing item concurrentlyScheduler executing item concurrently


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