SOAP API request timeout in production environment

Erik McKelvey 0 Reputation points
2023-12-22T05:02:28.66+00:00

Hello,

I have run into an issue where our SOAP web API is timing out after almost exactly 3 minutes and 50 seconds. When running the API locally requests never timeout (even when taking much longer). This leads me to believe there is a configuration option to prevent this from happening but I can't find one.

The application is deployed to an Azure Web App that provides other services among this one.

Just a point in the right direction would be extremely helpful.

Thanks!

Erik

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
8,930 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 22,706 Reputation points Moderator
    2023-12-22T07:18:50.8433333+00:00

    @Erik McKelvey Thanks for reaching out to Q&A.

    Some commands in your build process may take longer than 60 seconds to produce any output. This is the default time limit for commands to run. If you need more time, you can increase the limit by setting the SCM_COMMAND_IDLE_TIMEOUT variable. For example, to set the limit to 10 minutes, use this command:

    SCM_COMMAND_IDLE_TIMEOUT=600

    Be aware that Azure has a general idle request timeout of 230 seconds. This means that clients will be disconnected if there is no response from the server within that time. However, the server will still continue to run the command after the disconnection.

    Reference- Link

    Also see- Why does my request time out after 230 seconds?

    Let us know if further query or issue remains.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.