Timeouts with long running ASP.NET MVC Core Controller HTTPPost Method

Question

I make use of ajax call in my ASP.NET Core MVC view pages

MyView.cshtml

          $.ajax({
                processData: false,
                contentType: false,
                data: new FormData(this),
                type: $(this).attr('method'),
                url: $(this).attr('action'),
                cache: false,
                success: function (data) {
                        $('#mydiv).html(data);
                        $('#bootstrapModal).modal('show');

Controller Post method"

    [HttpPost]
    [ValidateAntiForgeryToken]
    public async Task<IActionResult> MyLongRunningMethod(MyViewModel viewModel)
    {
        await MyProcess.Longprocess1();
        await MyProcess.Longprocess2();
        await MyProcess.Longprocess3();
        await MyProcess.Longprocess4();
        return PartialView("_MyPartialPage");
    }

This works but only has an issue for a long running process. I get the following error during debug mode when the process takes longer than around 2 minutes

I understand this is to do with expiration timeout

in previous versions of ASP.NET MVC you can apparently increase the timeout in your asp.net controller action.

HttpContext.Current.Server.ScriptTimeout = 90000;

However this doesn't exist in ASP.NET Core

I want to increase the timeout for debugging and deployment for a particular asp.net controller.

For production I can set it globally in the web.config by adding requestTimeout to the existing httpPlatform tag. e.g. for 10 minutes

<httpPlatform requestTimeout="00:10:00" ....

A similar question was asked but the answer giving using an CancellationToken but reading it, it doesn't seem it can help me with the timeouts.

How do I set the timeouts in Visual Studio 2015 debug mode like I can do when I deploy it?
IS there a per controller timeout setting like there was in ASP.NET 4?

Changes in VS debug mode described below. stackoverflow.com/questions/49172284/… — Piotr Maslanka
– Piotr Maslanka, Commented Mar 30, 2018 at 15:04

Dmitriy · Accepted Answer · 2022-08-01 13:39:02Z

63

But in .Net Core 2.0 there is no web.config file in project. It generate automatically.

I solved the problem by adding .UseKestrel(...) to the BuildWebHost function in Program.cs file as follows:

public static IWebHost BuildWebHost(string[] args) =>
    WebHost.CreateDefaultBuilder(args)
        .UseStartup<Startup>()
        .UseKestrel(o => { o.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(10); })
        .Build();
}

... Update for .net Core 6 ...

in Program.cs file after

var builder = WebApplication.CreateBuilder(args);

add ConfigureKestrel for WebHost like this

builder.WebHost.ConfigureKestrel(c =>
{
   c.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(15);
});

edited Aug 1, 2022 at 13:39

answered Feb 11, 2018 at 15:02

Dmitriy

7947 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Syaiful Nizam Yahya Over a year ago

This would be the best answer as by default web.config is not in the project.

Chaitanya Gadkari Over a year ago

This did not solve my issue, I still get 502 error, maybe because web.config is present in the project

Dmitriy Over a year ago

Do you have 2.0 project?

user2475096 Over a year ago

when you publish the application with "dotnet publish" it generate the web.config so you can modify it

ihebiheb Over a year ago

one important thing to note here is that will only work in Out-of-process hosting model as The requestTimeout attribute doesn't apply to in-process hosting : learn.microsoft.com/en-us/aspnet/core/host-and-deploy/…

|

Tullo_x86 · Accepted Answer · 2018-07-17 00:00:28Z

54

Setting the RequestTimeout="00:20:00" on the aspNetCore tag and deploying the site will cause it not to timeout.

Issue now only occurs when running from Visual Studio debug mode but not in release mode.

Take note: In ASP.NET RTM the httpPlatform tag has been replaced with aspNetCore in the web.config

Example for ASP.NET Core

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <handlers>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/>
    </handlers>
    <aspNetCore requestTimeout="00:20:00"  processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false"/>
  </system.webServer>
</configuration>

edited Jul 17, 2018 at 0:00

Tullo_x86

2,67326 silver badges27 bronze badges

answered Jul 21, 2016 at 14:59

devfric

7,5847 gold badges42 silver badges53 bronze badges

7 Comments

EthR Over a year ago

Using .net core 1.1 now and this seems to be working!

Naila Akbar Over a year ago

@firste did you find any solution for debug mode??

user1527312 Over a year ago

If you are running in Visual Studio, try to run in Console Mode instead of IIS. You should see an option that is the same name as your solution name in the dropdown that shows IIS, and this option does not seem to have the timeout limit.

rook Over a year ago

Works with 2.0 too

Barak Gall Over a year ago

Note, I don't think this works with .net core 3.1+ if you are using in-process hosting. requestTimeout is apparently not supported for this hosting model.

|

gezzahead · Accepted Answer · 2017-12-14 08:44:38Z

24

In my case we still had the 502 timeout error at 2 minutes even after updating the requestTimeout parameter. It turned out that kestrel has a 2 minute keep alive timeout which needed to be overridden:

var host = new WebHostBuilder()
               .UseKestrel(o =>
                    {
                        o.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(30);
                    }
                )

answered Dec 14, 2017 at 8:44

gezzahead

1,2761 gold badge12 silver badges20 bronze badges

2 Comments

AndrewBenjamin Over a year ago

'KestrelServerOptions' does not contain a definition for 'Limits'. This is not an ASP.NET Core 1.0 solution.

Captain Prinny Over a year ago

Appears to exist in 2.2

Thabiso Mofokeng · Accepted Answer · 2021-02-16 15:06:36Z

21

The accepted answer has changed since .Net Core 3.1. In NET Core 3.1 use the following implementation to increase KeepAliveTimeout:

Program.cs

public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseStartup<Startup>();
                webBuilder.ConfigureKestrel(options =>
                {
                    options.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(15);
                });
            });

Web.Config (You need to add the config file to your project if it doesn't exist.)

Increase requestTimeout as required on the web.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <handlers>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified"/>
    </handlers>
    <aspNetCore requestTimeout="00:15:00"  processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
  </system.webServer>
</configuration>

edited Feb 16, 2021 at 15:06

answered Jun 28, 2020 at 22:25

Thabiso Mofokeng

7599 silver badges23 bronze badges

3 Comments

toy Over a year ago

thx for this - just confirming: is this an AND or an OR ie, do both or one or the other?

Thabiso Mofokeng Over a year ago

@toy I had to do both to get it working properly.

Ross Presser Over a year ago

Web.config requestTimeout still won't do anything at all if you are hosting inprocess.

adiga · Accepted Answer · 2019-06-26 10:21:23Z

9

for me this worked:

public static void Main(string[] args)
{
    CreateWebHostBuilder(args).Build().Run();
}

public static IWebHostBuilder CreateWebHostBuilder(string[] args) =>
    WebHost.CreateDefaultBuilder(args)
        .UseStartup<Startup>()
        .ConfigureKestrel(o => { o.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(10); });

edited Jun 26, 2019 at 10:21

adiga

35.4k9 gold badges65 silver badges88 bronze badges

answered Jun 26, 2019 at 10:15

Alireza Marhamatabadi

1191 silver badge5 bronze badges

Comments

Rtype · Accepted Answer · 2022-03-22 02:27:07Z

4

For .net core 6.0

var builder = WebApplication.CreateBuilder(args);

builder.WebHost.ConfigureKestrel(t =>
{
   t.Limits.KeepAliveTimeout = TimeSpan.FromMinutes(15);
});

answered Mar 22, 2022 at 2:27

Rtype

91413 silver badges35 bronze badges

Comments

Edjaine Soares · Accepted Answer · 2019-07-23 21:50:23Z

0

In Visual Studio not appear file web.config in Solution Explore. I fixed adding the file in Solution and changed the property "Copy to output Directory".

answered Jul 23, 2019 at 21:50

Edjaine Soares

12 bronze badges

Collectives™ on Stack Overflow

Timeouts with long running ASP.NET MVC Core Controller HTTPPost Method

7 Answers 7

6 Comments

7 Comments

2 Comments

3 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

6 Comments

7 Comments

2 Comments

3 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related