On Tue, Apr 24, 2012 at 2:38 PM, Oleg Kalnichevski <[email protected]> wrote:
> On Tue, 2012-04-24 at 07:46 -0700, Mohit Anchlia wrote: > > We are few times a day see high response times and we suspect it might > have > > to do with firewall dropping connection because of tcp keep alive. Even > > though we have set to expire connection before that, I would still like > to > > confirm that this is not an issue. Is there a easy way to monitor how > long > > it takes for the httpclient to create a new connection or if it first > > timedout because of dropped connection and then created a new connection? > > This is in production so would like to know the safest approach. > > You can create a custom SchemeSocketFactory implementation or decorate > one of the existing ones and measure the time elapsed in #connectSocket > method in order to find out how long it took to establish connection to > the remote host. > > Thanks! Is the retry mechanism because of bad socket built in this method? If there is a dropped connection by firewall, is that seamlessly taken care of by this method? Or does it try to take another connection from the pool. We use pool of connections. > Hope this helps > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
