Hi Prasant
The http_socket_timeout is generally the one you want to change.
The settings are descrtibed here :
Configure the Proxy Service Settings Manually - CA Single Sign-On - 12.52 SP1 - CA Technologies Documentation
but a bit more :
Parameter | Discussion |
---|
http_socket_timeout | It depends on how long it takes your backend server to start responding, normally requests are quite quick, but if you have slow requests then they will need to extend that setting. It is important to note that it is not the entire time needed to return the resulting page, but only the time until the page is started to be returned. For example if a request returnes a large video it will usually start streaming data quite quickly, even if it takes some time to complete. The real problem are long database queries, where maybe it may take several min to complete the query before the backend returns any data. |
http_connection_timeout | This one is simpler and tends to cause less trouble mostly set to zero as per the manual: Defines the time, in milliseconds, spent on host name translation and establishing the connection with the backend server when creating sockets. |
The problem with long http_socket_timeout values is that you need some appreciation of what happens when the system is under load, or when the backend server goes down.
If the backend server goes down then ALL your reqeusts can take the 10min time, (and then times three as it retries), and that can hold up your worker pool threads in both proxy-engine and httpd.
Here was a setup that would allow you to avoid that:
TechTip - Configure Agent Gateway/SPS to avoid one bad back-end taking down all AG/SPS traffic.
Cheers - Mark
----
Mark O'Donohue
Snr Principal Support Engineer - Global Customer Success