HTTP 504 Gateway Timeout in Edge Private Cloud 4.16.09
Hi everyone,
I've tried changing all the timeout settings for both router and message processor which were outlined in the below community post, yet I still see an HTTP 504 Gateway timeout after ~57000ms when hitting my service. I expect the response to complete in roughly 120 seconds, hence the need to augment the timeout settings.
Community post:
https://community.apigee.com/articles/36324/apigee-private-cloud-performance-optimization.html
I changed the config values using the best practices, as described here:
http://docs.apigee.com/private-cloud/latest/how-configure-edge
My config files look like this:
[root@ilapg application]# pwd /opt/apigee/customer/application [root@ilapg application]# ls message-processor.properties router.properties [root@ilapg application]# cat router.properties conf_router_ServerContainer.io.timeout.millis=620000 conf_router_Client.pool.iotimeout=610000 conf_http_HTTPTransport.io.timeout.millis=600000 [root@ilapg application]# cat message-processor.properties bin_setenv_min_mem=1024m bin_setenv_max_mem=6144m bin_setenv_max_permsize=1024m conf_nodejs_connect.ranges.denied= conf_http_HTTPTransport.io.timeout.millis=600000
When I restart the RMP, I do see the output saying that the above config values have been updated as expected. However, there is no effect on behavior.
What timeout setting am I missing here? I can't seem to find anything written about this in the documentation either. Thanks in advance for your help!
Best,
Chris
Best Answer
In 4.16.09 the Nginx router has another property proxy_read_timeout that controls the IO timeout value. I suspect that this value is probably set to 57 seconds and hence you are seeing the Gateway timeout (504).
Please follow the steps outlined in the community post here to set the proxy_read_timeout to a higher value.
Retry the API calls and see if it works.
Thanks,
Amar
