Question
Truist
US
Last activity: 12 Oct 2017 10:15 EDT
PEGA0020 and socket timeouts seen in PROD
Most of the service responses are responding within 1 second (which is the default threshold setting value for service response timeout), but for the same service requests we are seeing “PEGA0020” alerts and “SocketTimeoutExceptions”.
Could you please let us know
• on which process it would have taken more time and why we are seeing these exceptions (root cause)
• on how can we avoid these issues
• if there is a way to avoid these issue without increasing the default threshold value
***Moderator Edit: Vidyaranjan | Updated SR details & Title***
Pegasystems Inc.
IN
Sometimes this exception will come due to network latency also, try to increase the response timeout on respective Connector and check once.
Pegasystems Inc.
IN
The first place to start investigating is to check your connector and see why the response is so slow.
Check what element it is returning and the size of it. If the amount of data returned by connector is huge, then think of redesigning it to restrict the data.
Truist
US
Thanks for your response, the problem we are seeing is that we are getting PEGA0020 alerts & Socket timeout exceptions even thought the service is responding within 1 second for the same request and same response (same data size in response). Could you please let know on which process it would have taken more time and causing these issues? is there a way to avoid these exceptions without increasing the threshold value?
Thanks in advance!
Pegasystems Inc.
IN
Is it happening for all environment or only specific environment ?
Also, is it happening across all locations ?