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: