On Wed, 2013-09-25 at 12:57 +0200, Sebastiano Vigna wrote: > On 25 Sep 2013, at 12:21 PM, Oleg Kalnichevski <[email protected]> wrote: > > > There are probably two most possibilities here: (1) there is a bug in > > HttpClient and the socket value does not correctly apply (I have tested > > such scenario on a number of occasions, so I do not find it likely), (2) > > the target servers keep on sending data either infinitely or at a very > > slow rate (in both cases the connection never reaches the level of > > inactivity for socket timeout to fire). > >
... > > It could be infinitely slow rate, but frankly netstat does not report *any* > open connection. > > Nonetheless, after about four hours, 41 out of 42 connections have exited. > > Any suggestion to patch this behaviour? One thing we can do is to track the > URLs that have caused such stalling connections. > I do not have any suggestions other than taking note of problematic hosts, monitoring them closely and probably applying more aggressive timeout parameters to those hosts by dynamically reducing socket timeout if throughput drops below a certain limit. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
