Hi Gurmeet, The MultiThreadedConenctionManager is invoked/created by Xfire Client, then how would I indicate Xfire Client to use/invoke IdleConnectionTimeoutThread?
-----Original Message----- From: Gurmeet Budhraja [mailto:guri.mailingli...@gmail.com] Sent: Friday, April 01, 2011 6:44 AM To: HttpClient User Discussion Subject: Re: Keep alive You can use IdleConnectionTimeoutThread for the same :) On Fri, Apr 1, 2011 at 12:41 AM, Vadheraju, Rajeshwar < rajeshwar.vadher...@fisglobal.com> wrote: > Yes, agreed. I think it is good idea to implement "retry" and "idle > connection handler" as opposed to "keep alive strategy". > How did you implement or use idle connection thread? I am using xfire as > my soap framework which uses MultiThreadedConnectionManager internally, > not sure how to tell xfire to use or run "IdleConenction Thread"? > > -----Original Message----- > From: Joan Balaguero [mailto:joan.balagu...@grupoventus.com] > Sent: Thursday, March 31, 2011 12:50 PM > To: Vadheraju, Rajeshwar > Cc: 'HttpClient User Discussion' > Subject: RE: Keep alive > > Hi Raj, > > In my case, I'm sending requests to "problematic" servers. By > "problematic" > I mean that they're abruptly closing the http sockets. > > That's why I'm not interested in keeping alive my http connections for > so > many time, because after few seconds (~10 seconds), they will be > probably > closed on the server side. > > In addition, it's also a good idea to implement an "IdleConnection > Handler" > to manage idle connections (and, in the same method, also call to > 'closeExpiredConnections', recommendation made by Oleg to me some months > ago) and also a 'Retry' handler. > > With this combination of strategies, you will minimize connection > problems > (like a 'Connection reset'), but you don't have to expect to solve the > problems completely. Using Http protocol, you ALWAYS will lose requests > due > to connection problems. > > Regards, > Joan. > > -----Mensaje original----- > De: Vadheraju, Rajeshwar [mailto:rajeshwar.vadher...@fisglobal.com] > Enviado el: jueves, 31 de marzo de 2011 18:19 > Para: HttpClient User Discussion > Asunto: RE: Keep alive > > Hi Joan, > I'm also researching on the same area. Could you please provide some > details why you are implementing keep alive strategy? > In other words, What problems prompted you to implement keep alive > strategy? If you could elaborate on your issue, I could share some of my > experience and research findings. > > Thanks, > Raj > > -----Original Message----- > From: Joan Balaguero [mailto:joan.balagu...@grupoventus.com] > Sent: Thursday, March 31, 2011 11:13 AM > To: 'HttpClient User Discussion' > Subject: Keep alive > > Hello Oleg, > > > > I've implemented a Connection Keep Alive strategy in my app, but I'm not > able to see what is the better way to check if it's working ok. Could > you > give any clue about how to do this? > > > > Thanks, > > Joan. > > _____________ > > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete > the > message and all copies; (ii) do not disclose, distribute or use the > message > in any manner; and (iii) notify the sender immediately. In addition, > please > be aware that any message addressed to our domain is subject to > archiving > and review by persons other than the intended recipient. Thank you. > _____________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > > > _____________ > > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > _____________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > > _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________ --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
