solutions that executiontimeout in an MVC project do not take effect

When we do Web server-side development, often encounter a demand scenario, because some time-consuming processing caused the page response processing time is very long, the technical point of view is whether to give the page processing program a specified time-out, the service-side handler execution time exceeds this specified timeout time interrupt processing, directly return the response, To prevent the server-side host to accumulate the throughput queue, resulting in total station paralysis.

In ASP. NET, there is such a convenient thing, he is executiontimeout.

Related Background executiontimeout properties (http://msdn.microsoft.com/zh-cn/library/vstudio/ System.web.configuration.httpruntimesection.executiontimeout (v=vs.100). aspx)

The Executiontimeout property indicates the maximum number of seconds allowed to execute before the request is automatically closed by ASP. The default value is 110 seconds. This time-out property is only applicable if the debug attribute in the <compilation> element is set to False.

If the time-out expires, an exception is thrown. You can record related information in the application folder of the event log. This is done by enabling application health monitoring in the

Tested validation found that the executiontimeout of the ASP. NET WebForm project is in effect. The executiontimeout does not take effect in the project in ASP. MVC3.

The MVC project allows executiontimeout to work with the solution that Web. config is currently only landed on the final page request processing controller and can be placed in the Basecontroller in the future http://forums.asp.net /p/1715081/4590486.aspx

Http://forums.asp.net/p/1715081/4579754.aspx?Re+web+config+executionTimeout+not+working+in+ASP+NET+MVC

Http://blog.miniasp.com/post/2011/09/08/ASPNET-MVC-Developer-Note-Part-22-About-httpRuntime-executionTimeout.aspx

solutions that executiontimeout in an MVC project do not take effect