Question
TForce Freight
US
Last activity: 2 Oct 2025 23:10 EDT
Socket Time Out Exceptionfor all REST API Calls in Pega 24.1.3
Hi All,
We are seeing the Socket time out exceptions in Pega for REST API calls when we test in the postman the time taken to respond is with in the range of the response timeout we provided on the service. Can you please provide your suggestions to resolve this Exceptions happening.
Thanks,
Rashmitha
HCA Healthcare
US
Likely causes are mismatched timeouts or network path differences between Pega and Postman. First, in your Connect REST rule set both Connect timeout and Read/Response timeout higher than your observed 95th percentile, and disable any very low “maximum response size” limits. Next, verify the run-time authentication profile and TLS/cert chain; Postman may trust a proxy cert that Pega does not. Check if a proxy/gateway is used from the Pega node (env vars, DSS, or load balancer); test the same URL from the Pega server with curl to compare latency. Enable wire/HTTP client debug logging on the Pega node to see whether the stall is during DNS, TCP connect, TLS handshake, or read. Reduce payload sizes and turn on gzip and chunking if supported. Increase connection pool size and keep-alive to avoid queueing under load. Finally, compare timeouts at every hop (API gateway, WAF, LB) and align them so upstream doesn’t close the socket before Pega finishes reading.