Support Article Read timed out exception in log



A systems administrator has received numerous complaints from the business regarding an error message appearing on the user screen.  When the error occurs, the user loses their work in the current business session.

Error Messages

The error message tha appears on screen is: Read timed out exception

From the Pega Logfile, the same error message is isolated:

2016-06-27 09:33:08,973 [00.140.79-80-exec-73] [          ] [                    ] [                    ] (      web.impl.WebStandardImpl) ERROR   - <IPADDRESS>: Problem retrieving input data: Read timed out
                at Method)
                at Source)
                at Source)
                at org.apache.coyote.http11.InternalInputBuffer.fill(
                at org.apache.coyote.http11.InternalInputBuffer.fill(
                at org.apache.coyote.http11.InternalInputBuffer$InputStreamInputBuffer.doRead(
                at org.apache.coyote.http11.filters.IdentityInputFilter.doRead(
                at org.apache.coyote.http11.AbstractInputBuffer.doRead(
                at org.apache.coyote.Request.doRead(
                at org.apache.catalina.connector.InputBuffer.realReadBytes(
                at org.apache.tomcat.util.buf.ByteChunk.substract(
                at com.pega.pegarules.web.impl.HttpUtilities.getPostBytes(
                at com.pega.pegarules.web.impl.HttpUtilities.extractRequest(
                at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(

This same error message is identified in the Pega ALERT log as an EXCP0001 ALERT.

Steps to Reproduce

Unknown.  This error seemingly appears at random on the user screen.  However, it is noted that this error occurs in the Pega logfile at the same time.

Root Cause

This problem is caused by an environment issue, such as:

- Server is trying to read data from the request, but its taking longer than the timeout value for the data to arrive from the client. Timeout here would typically be tomcat connector -> connectionTimeout attribute.
- Client has a read timeout set, and server is taking longer than that to respond.
- This error can happen with high concurrency if the keepalive is enabled.


A possible solution for this problem within the Tomcat web application is to modify the CONTEXT.XML file, and modify the CONNECTOR definition that governs the workstation browser connectivity to the Tomcat server.

    <Connector port="7181" protocol="HTTP/1.1"

Specifically, modify the connectionTimeout value.  Increase this value to supress the error condition.

Published July 7, 2016 - Updated August 12, 2016

Have a question? Get answers now.

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