Did you set the CoreConnectionPNames.SO_TIMEOUT somewhere in your code? According to the httpclient-tutorial.pdf, if you didn't set the socket timeout, your read operation should never be timed out. Here's the copied and pasted section from the PDF.
CoreConnectionPNames.SO_TIMEOUT='http.socket.timeout': defines the socket timeout (SO_TIMEOUT) in milliseconds, which is the timeout for waiting for data or, put differently, a maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout. This parameter expects a value of type java.lang.Integer. If this parameter is not set, read operations will not time out (infinite timeout). Good luck! dc On Mon, May 20, 2013 at 4:36 PM, rnavarrocantu <[email protected]>wrote: > Guys, I'm having this same issue, but it's not clear to me if there was a > resolution, and what was the settings required to avoid hitting this > timeout. Thanks > > > > -- > View this message in context: > http://httpcomponents.10934.n7.nabble.com/HttpClient-with-PoolingClientConnectionManager-throws-read-time-out-tp18437p20125.html > Sent from the HttpClient-User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
