Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SocketTimeoutException causes performance issues



Errors and thread dumps related to performance issues are generated  in the logs.

Error Messages

[WebContainer : 4] [/$STANDARD] [your_app:01.01.01] (ector.Rule_Connect_REST.Action) ERROR - Read timed out
[WebContainer : 4] [/$STANDARD] [your_app:01.01.01] (internal.mgmt.Executable) ERROR - Exception Caught unhandled exception: Read timed out at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.step6_circum0( at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pegarules.generated.activity.ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.step7_circum0( at com.pegarules.generated.activity.ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pegarules.generated.activity.ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.step11_circum0( at com.pegarules.generated.activity.ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity( at com.pegarules.generated.activity.ra_action_getworklist_24c2802c42dace909533a3424f471d8a.step2_circum0( at com.pegarules.generated.activity.ra_action_getworklist_24c2802c42dace909533a3424f471d8a.perform( at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( at com.pegarules.generated.html_section.ra_stream_automatenextassignment_57f2563ee530506d780d232d66f9e94d.simpleLayout_4(

Steps to Reproduce

Not Applicable

Root Cause

Search was implemented using a REST connection instead of the standard Search mechanism. The Read timeout error occurred because the response took longer than the timeout configured on the Connect-REST rule. When these connections timeout, ElasticSearch threads haung and caused performance issues.


Perform either of the following local-changes such that results are returned quickly:
  • Increase the timeout of the Connect-REST rule.
  • Increase the performance of the REST connection.

Published December 27, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us