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 ...7.2.2 Schduler exceptions for timeout7.2.2 Schduler exceptions for timeout
Previous
 
Next
New Post
7/7/2014 9:57 AM
 

I have dozens of scheduler exceptions in my event viewer.

They all seems to happen for timeout but the site is really small and does very few (~70 daily) visits. The server is not under heavy weight as well. The application pool is set to recycle only at fixed time (during night at 3AM)

So there must be something interfering. 

AssemblyVersion 7.2.2 PortalID -1 PortalName UserID -1 UserName ActiveTabI 

AssemblyVersion:7.2.2

PortalID:-1

PortalName:

UserID:-1

UserName:

ActiveTabID:-1

ActiveTabName:

RawURL:

AbsoluteURL:

AbsoluteURLReferrer:

UserAgent:

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:b3ae65ff-b001-4719-9e1d-86baa3bfbe6a

InnerException:Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:

StackTrace:

Message:

System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
   at DotNetNuke.Data.PetaPoco.PetaPocoExt.ExecuteReader(Database database, String sql, Object[] args)
   at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteReader(String connectionString, CommandType type, String sql, Object[] args)
   at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.LoadQueueFromTimer()
   at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.Start()
ClientConnectionId:07f97b4c-5568-4741-9a1b-f2e228c79dd9

 

I also have lots of failed scheduled index search (but on different times than those exceptions it seems)

THREAD ID 8 TYPE DotNetNuke.Services.Search.SearchEngineScheduler DOTNETNU 

THREAD ID:8

TYPE:DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE

EXCEPTION:Thread was being aborted.

RESCHEDULED FOR:1/1/0001 12:05:00 AM

SOURCE:STARTED_FROM_TIMER

ACTIVE THREADS:-2

FREE THREADS:3

READER TIMEOUTS:0

WRITER TIMEOUTS:0

IN PROGRESS:0

IN QUEUE:6

Nome Server:LEASEWE-6FLU4MF

 
New Post
7/8/2014 12:44 PM
 
I'm trying to fix that one that is still present in 7.3.1 (I upgraded but this didn't fix it).
One simple question... in 7.3.1 the option to set the scheduler on timer or request is gone right? I cannot find anywhere so I assume now its set on timer by default with no choice right?
 
New Post
7/8/2014 7:08 PM
 
Max, the option has been moved to Host > Scheduler.
Timeout is usually a performance issue (though that's sth, I don't know about ;))

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/9/2014 9:32 AM
 
Thank you boss, found the setting.
About the issue there must be something else, it cannot be a performance issue the site is tiny and not visited. The search indexing job takes <1 sec.
Another thing I have no scheduled events failures, just scheduler exception and most of all it seems when this happen the exception are logged 2-3 times just like if the process has been launched 2-3 times in a row:

09/07/2014 04.13.39Scheduler Exception AssemblyVersion 7.3.1 PortalID -1 PortalName UserID -1 UserName ActiveTabI
09/07/2014 04.13.39Scheduler Exception AssemblyVersion 7.3.1 PortalID -1 PortalName UserID -1 UserName ActiveTabI
09/07/2014 01.11.27Scheduler Exception AssemblyVersion 7.3.1 PortalID -1 PortalName UserID -1 UserName ActiveTabI
09/07/2014 01.11.12Scheduler Exception AssemblyVersion 7.3.1 PortalID -1 PortalName UserID -1 UserName ActiveTabI
09/07/2014 01.11.11Scheduler Exception AssemblyVersion 7.3.1 PortalID -1 PortalName UserID -1 UserName ActiveTabI

In the logs:

2014-07-09 04:13:37,446 [LEASEWE-6FLU4MF][Thread:28][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at PetaPoco.Database.ExecuteScalar[T](String sql, Object[] args)
at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteScalar[T](String connectionString, CommandType type, String sql, Object[] args)
at DotNetNuke.Data.DataProvider.AddScheduleHistory(Int32 ScheduleID, DateTime StartDate, String Server)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.AddScheduleHistory(ScheduleHistoryItem scheduleHistoryItem)
ClientConnectionId:c33b899c-1c9e-44d8-ae95-ed2ce834dfd8

In the event viewer:
AssemblyVersion:7.3.1
PortalID:-1
PortalName:
UserID:-1
UserName:
ActiveTabID:-1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:cb531944-5905-45eb-b396-7f8b8125a2b0
InnerException:Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
StackTrace:
Message:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at PetaPoco.Database.ExecuteScalar[T](String sql, Object[] args)
at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteScalar[T](String connectionString, CommandType type, String sql, Object[] args)
at DotNetNuke.Data.DataProvider.AddScheduleHistory(Int32 ScheduleID, DateTime StartDate, String Server)
at DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.AddScheduleHistory(ScheduleHistoryItem scheduleHistoryItem)
ClientConnectionId:c33b899c-1c9e-44d8-ae95-ed2ce834dfd8


But I don't understand how I can go deeper investingating this or if it's a core platform bug. The scheduler is set to run on timer.
This is the site crawler job history, just to give you an idea that this cannot be a performance issue:


Search: Site Crawler Starting. Content change start time 7/9/2014 2:53 PM
Tabs Indexed: 0
Modules (Metadata) Indexed: 0
Modules (Content) Indexed: 6
Users Indexed: 1
Total Items Indexed: 7
Indexing Successful 0,89
S: 09/07/2014 15.23.44
E: 09/07/2014 15.23.45
N: 09/07/2014 15.53.44
Search: Site Crawler Starting. Content change start time 7/9/2014 2:23 PM
Tabs Indexed: 0
Modules (Metadata) Indexed: 0
Modules (Content) Indexed: 6
Users Indexed: 0
Total Items Indexed: 6
Indexing Successful 0,687
S: 09/07/2014 14.53.33
E: 09/07/2014 14.53.33
N: 09/07/2014 15.23.33
Search: Site Crawler Starting. Content change start time 7/9/2014 1:53 PM
Tabs Indexed: 0
Modules (Metadata) Indexed: 0
Modules (Content) Indexed: 6
Users Indexed: 0
Total Items Indexed: 6
Indexing Successful 0,53
S: 09/07/2014 14.23.28
E: 09/07/2014 14.23.29
N: 09/07/2014

It take less than a second.
 
New Post
7/9/2014 9:42 AM
 
Is your database on the same box as your web server? If not, it could be a connection issue between the web server and DB server. It could also be slow processing by the DB Server. The "DotNetNuke.Services.Scheduling.Scheduler.CoreScheduler.AddScheduleHistory" is pretty much a straight shot to a SQL call with very little code in-between.

Best,
Kelly

Create simple forms or build complete module solutions XMod Pro is the best-selling forms and views module of all time.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...7.2.2 Schduler exceptions for timeout7.2.2 Schduler exceptions for timeout


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out