Support Article
SocketTimeoutException causes performance issues
SA-68901
Summary
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 - java.net.SocketTimeoutException: Read timed out
[WebContainer : 4] [/$STANDARD] [your_app:01.01.01] (internal.mgmt.Executable) ERROR - Exception com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: java.net.SocketTimeoutException: Read timed out at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.step6_circum0(ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.java:1811) at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.perform(ra_action_pyinvokerestconnector_e8e118414a520bb18367337b0b748d90.java:154) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527) at com.pegarules.generated.activity.ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.step7_circum0(ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.java:1002) at com.pegarules.generated.activity.ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.perform(ra_action_invoke_4dc028ab25da14c2d6798b84993f966a.java:172) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527) at com.pegarules.generated.activity.ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.step11_circum0(ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.java:1006) at com.pegarules.generated.activity.ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.perform(ra_action_getuserworklist_e0f27d4467ff02bafefd65da262560ff.java:267) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527) at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10674) at com.pegarules.generated.activity.ra_action_getworklist_24c2802c42dace909533a3424f471d8a.step2_circum0(ra_action_getworklist_24c2802c42dace909533a3424f471d8a.java:248) at com.pegarules.generated.activity.ra_action_getworklist_24c2802c42dace909533a3424f471d8a.perform(ra_action_getworklist_24c2802c42dace909533a3424f471d8a.java:91) at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527) at com.pegarules.generated.html_section.ra_stream_automatenextassignment_57f2563ee530506d780d232d66f9e94d.simpleLayout_4(ra_stream_automatenextassignment_57f2563ee530506d780d232d66f9e94d.java:428)
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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.