Increase io.timeout.millis value.

[#1]

Typically, the timeouts are set to 60 seconds on our runtime components, so you might see calls returning 504 after 60 seconds. Does your backend take more than 60 seconds to respond ?

[#2 · Accepted solution]

If backends takes more than 60 sec to respond then we can increase the timeout from default 60 seconds to more.

The timeout is usually set in tapering fashion (load balancer (60)>router(58)>message-processor(55), and for the trial accounts this is not something that we can change on-demand.

If you are a paid customer, or have an on-premise installation then this can definitely be modified to suit your needs.

The timeouts should only need to be set only in the HTTPTargetConnection section.for example to increase the timeout settings to 5 mins we can configure HTTPTargetConnection as below :

<HTTPTargetConnection>

<Property name="io.timeout.millis">300000</Property>

</HTTPTargetConnection>

Please not that all the components must be configured to support at least above timeout. So, for example, your Load Balancer should be set to, say 306000, the router to 304000, and the MP set to 302000, and then the proxy set to 300000.

This scenario ensures no "orphaned" connections. These must be set to the highest acceptable level. Then, in the individual proxies (that don't need the higher timeouts), you would be able to set lower values in the Proxy "bundle”.