Understanding Rest API timeout
Few questions around timeouts around Rest API call as a client :
a) What is the purpose of Response Timeout in Connect-REST form?
b) What happens when the connection to the server is successful but takes long to respond and Response Timeout value expires? E.g. Response timeout = 40 secs. Response from server takes 80 secs. Will Pega release all the threads and terminates the connection? If yes, then will the connection be aborted from application server as well?
c) Does socket time out happen because shorter Response Timeout value?
d) Is there a way to abort an API connection if it's taking too long?
Thanks
Accepted Solution
Updated: 9 Jan 2025 11:03 EST
Pegasystems Inc.
CA
Please find the comment
a) Response timeout field, enter the number of milliseconds after which this rule times out with a failure message if it does not receive a response. Enter zero or leave blank to wait indefinitely.
This field is disabled and ignored at run time when the Intended for field is set to queuing.
b) I think Yes
d) I believe you're looking for a manual abort by the user - I don't think so
Updated: 9 Oct 2024 13:46 EDT
TD Bank
CA
@RameshSangili thanks for the response. Do you know in the backend what is the response timeout set to in the Java code?
E.g. Is it setting
socket.setSoTimeout(pega_connector_reponse_timeout)
? where socket is Socket Object (Socket socket = new Socket())