Timeout Configuration for NodeJS

[#1]

I am facing an issue wherein the browser responds with a timeout after 100 seconds for a NodeJS application. I am pretty sure that the process is going on right. Its just that it will require more time to finish its job. I want to increase the timeout value so that it doesn't result in a timeout

[sarthak]

Hi @DATASTREAMX-TEST If you are using Apigee in private cloud i.e. On-prem please refer to the thread here : https://community.apigee.com/questions/3957/io-timeout-configuration-for-nodejs-target.html.

If you are using Apigee in the cloud please raise a support ticket and Apigee support can let you know if this is configurable in the cloud or not.If you do not ha

Thanks

[vineet_vineetb]

Hi @sarthak We are facing a similar issue where from the node app we are making node.js request calls to backend services. We are getting a timeout after 110 seconds. Any idea where the 110 seconds timeout could be happening?

[#4]

@Vineet Bhatia

check the below property which is part of the node.js properties in Mp . Looks like there is some issue with your backend .

Can you curl to your backend from that machine and check if you see the same issue ?

# Set to zero to disable this timeout. # The default is 110. http.request.timeout.seconds=110

[adas]

@DATASTREAMX-TEST and @Vineet Bhatia This is controlled by a property called http.request.timeout.seconds in the message-processors' nodejs.properties file.

# If an API call does not write to the HTTP "output" stream after this period of time,

# we will raise a 503 error with an error code to that affect.

# Set to zero to disable this timeout.

# The default is 0.

http.request.timeout.seconds=110

This was previously set to 110 seconds. With the next Apigee Edge cloud release, this would be set to 0 so that you don't face this issue any more. If you are an on-premise customer, you can set the value to 0 on the message-processors and restart them. It should work fine.