Both HttpClient v3 and v4 have the "issue" where the sockets of connections released back to pooling connection managers are moved to a CLOSE_WAIT state in case they are to be used again for some other request to the same host. I know that the following methods can be used to close out idle connections programmatically: v3 - HttpConnectionManager#closeIdleConnections(long) v4 - ClientConnectionManager#closeIdleConnections(long, TimeUnit)
Do either of the v3 or v4 pooling connection managers support closing down idle after an elapsed period of disuse? If so, how does one enable that? I wasn't able to find any settings in the docs that I thought were related so I'm guessing the answer to my first question is "no". -- Chad La Joie www.itumi.biz trusted identities, delivered --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
