Node request getting timed out after 30 seconds

[rahilkhan4u]

I have a node application deployed on BTP space, All the of request are getting timeout after 30 seconds.

I have tried setting the request timeout manually to 2 minutes from UI and from node itself, But nothing works. After going through lots of blogs, I found that there are some server level settings where the node application is deployed. Is there any way to change the files of server or setting of the server from node application?

Thanks in Advance.

For testing purpose I created below endpoint and waiting for 2 minutes before sending the response.

But when I hit this endpoint from UI, the request only last for 30 seconds and it gets timed out. This is how I am calling this endpoint.

Also note that, Request is getting timed out only after deployment, it is working fine on local.

[frank_essenberger1]

Hello Rahil,

the issue is really broad and it is not clear what you are calling and how. If you use the SAP cloud SDK to make the HTTP request in a JavaScript application you can set the timeout like on any http client. In order to get support you should provide the following information:

- Give a code sample how you make the call

- Is it expected for the call to take that long? If not huge amounts of data are send a request should not take 30 seconds or two minutes.

- Make a connectivity test in your BTP account using some request which is fast to ensure that your setup is ok and the timeout is not related to a connectivity issue.

Best

Frank

[rahilkhan4u]

Thank You for the response Frank.

I have added the required information in the question now.

I am doing some data processing in node application, it is expected to take little long, When I hit the same endpoint on Local, it return response in around 2 minutes 25 seconds. But when hit the same end point after deployment, it gets timed out in 30 seconds, Not just this request but all the request which are expected to take some time are getting timed out in 30 seconds.

Also I don't think this is a connectivity issue because I have tried it on different network at different interval of time and if it was a connectivity issue then request should have timed out at different internal of time, each time it is getting timed out in exactly 30 seconds.

[frank_essenberger1]

Hi Rahil,

thanks for the info. The way you set the timeout is right in axios. Also that it works locally seems to indicate that the code is correct. Unfortunately I can not really help here because in the SDK we use also axios latest version which I assume is the same you use. You could also try node fetch to see if it is a problem with the client.

This would mean there is some difference in running the application locally and on the cloud. Have you compared the node version used? This has an effect on the http agent used. I hope the colleagues from the BTP see this issue and comment on it. They should know if there is something killing long running request - I really doubt this to be honst and assume it is a difference in used node versions or so.

When I googled it quickly there was a default server.timeout in node 13 and below set to 2minutes per default. This was dropped in new node version to a value of 0 meaning no timeout. So please ensure you are using node 14 or above - which you did locally most likely but not on BTP.

Best

Frank

[frank_essenberger1]

see here: https://stackoverflow.com/questions/23874954/is-there-a-default-timeout-in-node-js-for-http-request

[rahilkhan4u]

Thanks Frank for the response, It seems the issue was in MTA file, As Jun suggested, We need to add timeout in mta.yml file under app service. Thanks for the support Frank. 🙂

[junwu · Accepted solution]

group: destinations 

properties: 

forwardAuthToken: true 

name: *** 

url: **** 

timeout: 600000<br>

can you try this in your yaml file?

[rahilkhan4u · Accepted solution]

Thank You for the Response Jun,

This how I have added the timeout parameter in the MTA file. Please confirm if this is okay.

[junwu · Accepted solution]

no.

it should be your ui app module, which requires service module as dependency.

[rahilkhan4u · Accepted solution]

Thanks alot Jun, After adding the timeout parameter in app service the issue gets resolved.

For others, this is where I added the timeout.

Thanks,

Rahil Khan