Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...DNN 6.2 Beta2 (1251) - Scheduler Errors Flooding the EventLogDNN 6.2 Beta2 (1251) - Scheduler Errors Flooding the EventLog
Previous
 
Next
New Post
4/29/2012 10:18 PM
 

I have a clean, new install of DNN CE 06.02.00 (1251) on Server 2008 R2/IIS7.5 using SQL 2008 R2. After creating 2 social groups and 2 users and playing around with the new settings the site started getting slow. I checked the server and CPU was slammed at 100%. I managed to stop the website and the appPool and get control of things. I ended up truncating the EventLog table and things went back to normal. Over the next 30 minutes things went downhill, another 100,000 EventLog records.

So the EventLog table is filling up with over 100k entries every 30 minutes or so. After playing around I narrowed things down. The two events flooding the EventLog table are SCHEDULER_EVENT_FAILURE (11) and SCHEDULER_EXCEPTION (3). They don't seem to include much info that I recognize from any past DNN experiences. So I started playing to see what I could do to make the flood begin.

Using the new Messaging starts it. I truncated the EventLog again after restarting the (IIS) site and recycling the appPool. Nothing in the EventLog for a while except for the Application Start entry. From the User Profile page I did Compose New Message. This started it, with no way to stop short of stopping the site and/or appPool.

I searched the Forums for "Scheduler" and went through a lot of posts, but didn't come across anything that seemed related and/or tied to 6.2 beta. I've put quite a bit of time in to narrowing this down. Hopefully someone can spot something I am missing.

Here are the contents of the two Exceptions:

1. Scheduler Event Failure  
THREAD ID: 19
TYPE: DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler
EXCEPTION: Object reference not set to an instance of an object
.
RESCHEDULED FOR: 1/1/0001 12:00:30 AM

SOURCE: STARTED_FROM_BEGIN_REQUEST

ACTIVE THREADS: -13045

FREE THREADS: 13046

READER TIMEOUTS: 0

WRITER TIMEOUTS: 0

IN PROGRESS: 0

IN QUEUE: 4
    -

2. Scheduler Exception  

AssemblyVersion: 6.2.0

PortalID: -1

PortalName:

UserID: -1

UserName:

ActiveTabID: -1

ActiveTabName:

RawURL:

AbsoluteURL:

AbsoluteURLReferrer:

UserAgent:

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: 019073b4-87ce-4686-af7a-9c6caf8745e0

InnerException: Object reference not set to an instance of an object.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.SendMessage

StackTrace:

Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.SendMessage(MessageRecipient objMessage) at DotNetNuke.Services.Social.Messaging.Scheduler.CoreMessagingScheduler.DoWork()

Source:


- Accuraty / Jeremy
 
New Post
4/29/2012 10:38 PM
 

Jeremy, one thing that might be worth checking is the scheduled item history. It sometimes logs additional information when a scheduled task fails. For example, I don't have my local SMTP server on and this is the message I receive in my schedule item history (for this specific task): 

Messaging Dispatch MessagingScheduler DoWork Starting d7c11d82-2c20-42a5-9efb-d64374f55422No SMTP Servers have been configured for this host. Terminating task. 

If you can post back here what you find, it would be appreciated. Thanks!


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
4/29/2012 11:08 PM
 
I don't see anything useful. Hosts / Scheduler shows the entries in Schedule History.

Messaging Dispatch
Seconds: 4263.6408594

No other info is recorded. There are 20+ entries like that in the history with times in seconds ranging from 79.x to the one above being the highest.

I doubt it is a factor, but for the record, SMTP is working just fine.

- Accuraty / Jeremy
 
New Post
4/29/2012 11:42 PM
 
I also upgraded another test-bed DNN install from 6.01.04 to 6.02 beta2 (1251) via the upgrade version. That was on a different server running Server 2003, IIS6, and SQL 2005. Same thing on there - about 200,000 entries, same 2 as above over and over again. So my only two experiments with Beta2, one a clean install on a modern server and the other an upgrade on an older server and both had the exact same issue when sending a message to a user.

One idle thought-guess. The message I sent may have been from the SuperUser host account - which in the old days of Active Social didn't have an associated profile. Since the error does mention the classic, "Object reference not set to an instance of an object" - I wonder if that is what might be initially tripping the error?

But the real issue to me seems to be the flooding. Hopefully someone can figure out a way to detect, recognize or wrap this so that the wildly errant thread can get shutdown somehow. Doesn't sound easy, but definitely necessary.

- Accuraty / Jeremy
 
New Post
4/30/2012 12:10 PM
 
this is a known error which has been fixed in the post-beta2 builds

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...DNN 6.2 Beta2 (1251) - Scheduler Errors Flooding the EventLogDNN 6.2 Beta2 (1251) - Scheduler Errors Flooding the EventLog


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