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/27/2008 7:14 PM
 

Maybe spoke too soon.  Just found the site crashed.  I changed the mode back to request mode, restarted the site then set it back to timer mode.  It is up again but I found the logs were a mess from today.  Here are a couple. What do you think this means?

10/27/2008 7:00:28 PM   General Exception       AssemblyVersion: -1; PortalID: -1; PortalName ...
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Unhandled Error:
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: Request timed out. --- End of inner exception stack trace ---
Source:
Server Name: WEB83
  10/27/2008 7:00:28 PM   Scheduler Exception       AssemblyVersion: 04.09.00; PortalID: -1; PortalN ...
AssemblyVersion: 04.09.00
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /cms/default.aspx
AbsoluteURL: /cms/default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1581821b-a038-4c6a-87f9-ba59da261131
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.AddQueueUserWorkItem
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.AddQueueUserWorkItem(ScheduleItem s) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.FireEvents(Boolean Asynchronous) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.RunEventSchedule(EventName EventName)
Source:
Server Name: WEB83
  10/27/2008 7:00:28 PM   Scheduler Exception       AssemblyVersion: 04.09.00; PortalID: -1; PortalN ...
AssemblyVersion: 04.09.00
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /cms/default.aspx
AbsoluteURL: /cms/default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3d363638-0a91-4f2a-8d13-9f82db821be5
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.Thread.SleepInternal
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.ProcessGroup.AddQueueUserWorkItem(ScheduleItem s)
Source:
Server Name: WEB83

joiseystud wrote
 

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. 

 
New Post
10/29/2008 8:05 AM
 

Those errors are what you get when something is hanging. You'll find a ton if them all within a couple of seconds of each other. The don't individually really give an indication of the cause, but you might find a clue at the beginning of the series of exceptions.

I'm very interested in the event queue, because mine is around 900 entries long and the majority of them look like old upgrade steps and stuff that was probably done once and not needed since.

Can anyone here perhaps clarify what all these events might be.. are they really all needed, are they possibly what is causing the trouble going into timer mode, can some of the entries even be removed... etc?

Rob

 
New Post
10/29/2008 1:29 PM
 

joiseystud wrote

Maybe spoke too soon.  Just found the site crashed.  I changed the mode back to request mode, restarted the site then set it back to timer mode.  It is up again but I found the logs were a mess from today.  Here are a couple. What do you think this means?

Joiseystud, please cross reference the errors you are getting via date/time with the scheduler log (see which schedules are being kicked off at that time). Thanks



Alex Shirley


 
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