I am hosting a asp.net 5 application on azure, the code is complied for beta8, the application runs fine on the local environment and when i publish the code on the azure si
This can also happen if you have an infinite loop in your code.
I recently had the same issue and was able to solve it by setting the requestTimeout
within the web.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath=".\PROJECT.exe" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:30:00"/>
</system.webServer>
</location>
</configuration>
For us its not related with code, appservice redeploy and then restart needs to be done
I was able to solve this issue by removing forwardWindowsAuthToken
from the web.config file under wwwroot.
httpPlatform
remove the forwardWindowsAuthToken="true/false"
propertyRedeploy and mine worked fine.
See here https://github.com/aspnet/Hosting/issues/364 for plenty of discussion
I got the same error. After searching some solutions, I changed the code, replacing the async method calls with non-async ones, regarding the notes that thread pool might exceed the allowed capacity. This did not work. Then I increased the request timeout in web.config to 20 minutes and it is resolved.
Add the string below in web.config file.
requestTimeout="00:20:00"
as
<aspNetCore processPath="dotnet" arguments=".\API.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:20:00" />
Today we had the same problem. In our case it was caused by a failing Debug.Assert(...)
.