We have configure a connect rest in our pega cdh container activity. With connect rest timeout as 3500ms. But even if it is timing out the threads are not closing. Due to this threads are getting saturated and we are getting huge 503,504 errors. Does anyone faced this and solved this issue.
Related topics
| Conversation | Replies | Views | Activity | |
|---|---|---|---|---|
| Connect soap: Connection idle timeout | 1 | 220 | May 23, 2024 | |
| pegarules.pub.services.ConnectorException: Caught unhandled exception: java.net.SocketTimeoutException: Read timed out | 4 | 4891 | April 19, 2022 | |
| Understanding Rest API timeout | 2 | 727 | October 9, 2024 | |
| is there any time out configuration we set in Pega environments Pega cloud? we observed some timeout issue | 1 | 164 | September 22, 2025 | |
| PEGA0011 alerts in production | 3 | 504 | March 27, 2023 |