HomeHomeUsing DotNetNuk...Using DotNetNuk...Administration ...Administration ...Scheduler in Timer Mode kills portalScheduler in Timer Mode kills portal
Previous
 
Next
New Post
10/27/2008 4: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 5: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 10:29 AM
 

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 DotNetNuk...Using DotNetNuk...Administration ...Administration ...Scheduler in Timer Mode kills portalScheduler in Timer Mode kills portal


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.

Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me
Charlotte DoDNN

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

r2integrated
Telerik JustCode Free
DotNetNuke DNN Hosting

DotNetNuke Scoop!

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.