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 ...HTTP Request Timeout Increase?HTTP Request Timeout Increase?
Previous
 
Next
New Post
3/31/2011 10:25 AM
 
How do I increase the HTTP Request Timeout in my web.config file? What should I be looking for?

I want to do this to avoid getting scheduler timeout errors in my event log.
 
New Post
3/31/2011 11:08 AM
 
Jdcboss

Scheduler should be in separate thread and HTTP Request Timeout should not take affect for it.

But sure you can change your timeout. Please add/change param executionTimeout within httpRuntime in your web.config.

Sergey
 
New Post
3/31/2011 2:06 PM
 
Thanks for the info... couple questions:



1. Here is the runtime code:



<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="2000000" requestLengthDiskThreshold="2000000" requestValidationMode="2.0" />



This seems ample... why do I get timeouts on the scheduler? Also I am on .NET 4.0 - is requestValidationMode="2.0" the correct value for .NET 4.0?





2. Also, here is my scheduler code in the webconfig file:



<scheduling defaultProvider="DNNScheduler">

      <providers>

        <clear />

        <add name="DNNScheduler" type="DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler, DotNetNuke.DNNScheduler" providerPath="~\Providers\SchedulingProviders\DNNScheduler\" debug="false" maxThreads="1" />

      </providers>

    </scheduling>





What does the maxThreads refer to?
 
New Post
4/4/2011 6:50 AM
 
jdcboss

Scheduler is in separate thread. It looks like your scheduler tries to connect to another external resource and takes timeout. There is no other reason why tiemout happens. We had schedulers working with eBay API and there were crazy big requests, but scheduler never been timeout.

What kind of code do you use inside of scheduler?

Sergey
 
New Post
4/4/2011 9:21 AM
 
Sergey,

I am not sure what other external resource this scheduler would connect out to - I know there are no sites on thsi instance that require any 'special care' - My next question would be this:

In the scheduler page, what is the bare minimum needed to run the DNN instance? Or what are optimal scheduler settings? This way I can check if there are things I don't need...


Purge Users Online Enabled Every 1 Minute Every 5 Minutes 4/4/2011 9:19:11 AM

Purge Site Log Every 1 Day Every 2 Hours

Purge Schedule History Enabled Every 1 Day Every 2 Days 4/4/2011 4:15:49 PM

Purge Log Buffer Every 1 Minute Every 5 Minutes

Send Log Notifications Every 5 Minutes Every 10 Minutes

Search Engine Scheduler Enabled Every 12 Hours Every 16 Hours 4/4/2011 4:24:47 PM

Purge Cache Every 2 Hours Every 30 Minutes

DNN Events Enabled Every 1 Hour Every 30 Minutes 4/4/2011 10:04:11 AM

Purge Module Cache Enabled Every 1 Minute Every 30 Seconds 4/4/2011 9:19:11 AM

Messaging Dispatch Enabled Every 1 Minute Every 30 Seconds 4/4/2011 9:19:11 AM

Newsfeeds Background Loader Enabled Every 10 Minutes Every 1 Hour 4/4/2011 9:29:09 AM

Right now above is exactly what I have in place... Let me know if something seems out of place.

Thanks.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...HTTP Request Timeout Increase?HTTP Request Timeout Increase?


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