Web Timing out Max setings

Currently I have my web config set up like this:
<system.web>
            <httpRuntime maxRequestLength="16384" executionTimeout="120"/>
            <authorization>
                  <allow roles="Admins"/>
            </authorization>
            <trace enabled="false" requestLimit="20" traceMode="SortByTime"/>

But still we are getting time outs.   How much farther can I go?

I suspect it has more to do with limited worker threads to the database.
TimSweet220Asked:
Who is Participating?
 
Kevin CrossChief Technology OfficerCommented:
Additionally, I am involved with another question that reminded me that there are also ConnectionTimeout and CommandTimeout values you can set if using SqlConnection and SqlCommand from your .NET as an example. Definitely need to ensure you have the right combination of timeouts for your application need. My main point above is that I do not believe you have the timeout in the web.config set to the MAX as I believe you are reading the incorrect attribute. The one of interest there is executionTimeout, which is Int32 so have a max of 2,147,483,647 -- well above 120 and any value I would put in that setting.

ConnectionTimeout has a default of 15 seconds.
CommandTimeout has a default of 30 seconds.

Hope that helps!
0
 
Kevin CrossChief Technology OfficerCommented:
You only have your executionTimeout set to 120 seconds or 2 minutes; therefore, (1) that is not too high and (2) what is the exact error you are dealing with? Are you getting a controlled timeout from application. Please clarify.
0
 
TimSweet220Author Commented:
Perfect...thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.