You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jon Moore (JIRA)" <ji...@apache.org> on 2011/07/15 21:02:01 UTC
[jira] [Resolved] (HTTPCLIENT-1108) different connection reuse
strategy would reduce number of open connections
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Moore resolved HTTPCLIENT-1108.
-----------------------------------
Resolution: Fixed
> different connection reuse strategy would reduce number of open connections
> ---------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1108
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1108
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 4.1.1
> Reporter: Jon Moore
> Assignee: Jon Moore
> Priority: Minor
> Fix For: 4.1.2
>
>
> Currently, the ThreadSafeClientConnManager reuses persistent connections in a round-robin fashion: when the connection is checked back into the pool, it is added to a queue of available connections for later use. This has the perhaps unintended effect that the client may keep open more connections than needed, because the "last used" time keeps getting updated and none of the connections can get reclaimed via closeIdleConnections().
> Exchanging the queue (FIFO) for a stack (LIFO) would result in extra connections actually becoming idle for long enough to be reclaimed.
> I have a working patch for this; just need to get my act together to get it in.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org