How does stale check actually work? By following the code it leads me to SessionInputBufferImpl class and there it is trying to read some data from the buffer. What data is it trying to read? How do we actually say that this connection is stale and close it?
The context behind this is we are seeing nearly 10K socket exceptions per minute on our box. and it all happens when it checks for stale connections and then trace ends with a SocketTimeoutException Our setup is pretty simple. We have 10 different routes. With 5 max per route. If I do a netstat on my box I can see exactly 50 TCP connections on my box all in ESTABLISHED state. But the above SocketTimeoutException doesn't make sense. As it all bubbles up in checking for stale connections so wanted to know how it worked. Thanks in advance. -- View this message in context: http://httpcomponents.10934.n7.nabble.com/4-3-3-Newbie-question-about-Stale-Check-tp28119.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
