On Tue, 15 Jun 2010 18:37:48 +0200, Laurent Perez <[email protected]> wrote: > Hello > > I'm trying to understand if the v3, which my application currently > uses, handles Keep-Alive properly - because our client says it does > not. > > On several requests, using lsof, I can see that httpclient connections > in state ESTABLISHED gradually fall back to a CLOSE_WAIT state, and > they also stay in this state, unless I explicitely call > org.apache.commons.httpclient.MultiThreadedHttpConnectionManager#closeIdleConnections. > A question : if Keep-Alive was working properly, should the > connections stay in ESTABLISHED forever ? >
I found a similar problem. I was using many connection managers (up to about 1000) to handle lots of connections over time to same host and I found that I would eventually hit a too many open files issue that crashed the application. My temporary fix was to reduce the timeouts increase ulimit and eventually remove the multi threaded connection manager and handle cookies manually. It was a sloppy fix but I'm hoping the 4.x version will allow me to use a single connection manager with many different states (cookie settings) for the same server. > Thanks for your input > laurent --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
