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

Connect-REST fails with Read timed out error



User is on Pega 7.2.1 and invokes a Connect-REST to search the orders.

The connector is returning socket timeout exception and returning no results.

The REST service when called from SOAP-UI returns result. The service returns data but Connect-REST times out irrespective of setting a very high timeout value.

Error Messages

Caused by: Read timed out
at Method)
at com.pega.apache.http.impl.conn.DefaultResponseParser.parseHead(
at com.pega.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(
at com.pega.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(
at com.pega.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(
at com.pega.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(
at com.pega.apache.http.protocol.HttpRequestExecutor.execute(
at com.pega.apache.http.impl.client.DefaultRequestDirector.tryExecute(
at com.pega.apache.http.impl.client.DefaultRequestDirector.execute(
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(
at com.pega.apache.http.impl.client.AbstractHttpClient.execute(

Steps to Reproduce

  1. Login to the application.
  2. Launch interaction portal. Click on new > Phone call.
  3. Search for customer type < dealer name > <dealer code>.
  4. Select the customer returned from the result and hit submit.
  5. Go to orders tab to display order list. This order list is populated using the response received by REST Connector but it times out irrespective of setting a very high timeout value on Connect-REST rule form.

Root Cause

A defect or configuration issue in the operating environment is identified as root cause.

The actual REST service end point URL is mapped to a reverse proxy URL.

The reverse proxy logs suggested that GET request is sent by Pega but the corresponding POST response is not received at the reverse proxy level.


Contact the infrastructure support team to make the configuration changes as needed on application server, reverse proxy, firewall sides so that the POST respone sent by REST service is received by Pega.

Published June 1, 2017 - 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