Forum Discussion
App Service Time out in 230 Sec
Rolf-42 Thanks.
So, The application runs both on Azure as well as on-premise. using a webjob or durable function will put a dependency on cloud.
I have couple of App Services. App Service 1 calls App Service 2, and if App Service 2 takes more than 230 seconds to respond, the request throws 500. I tried Async Await and
Hello Biplab Sah
As you can see from this link https://en.wikipedia.org/wiki/List_of_HTTP_status_codes an error 500 is an internal server error. So you need to do some debugging in the call between service 1 and service 2 like which authentication, which permission, which URL/URI etc.
And yes, going towards async is a good cloud development principle. Maybe you can also consider putting your apps into containers to reduce dependencies to cloud services.
Some source code would help to get into the details but again that is probably better asked in the developer community than in the Microsoft Learn community.
Good luck
Cheers
Rolf
#MCT #LearnWithRolf #TheCloud42
- Biplab SahJul 16, 2020Copper ContributorThanks Rolf-42
I do understand the scenario. the same application run great on IIS. it's an issue of app service request time out, which I have narrowed down and tested.
check this: https://github.com/MicrosoftDocs/azure-docs/issues/30795
As per your suggestion, I have put the question in the other group too: https://techcommunity.microsoft.com/t5/apps-on-azure/app-service-timeout-in-230-sec/m-p/1526934
Thanks,
Biplab