[
https://issues.apache.org/jira/browse/HTTPCLIENT-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-1760.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0 Alpha2
4.5.3
Added protected methods to enumerate leased and available connections to SVN
trunk and 4.5.x branch. Please review / test and close this issue.
Oleg
> PoolingHttpClientConnectionManager has no option to close long leased
> connections
> ---------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1760
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1760
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.4.1, 4.5
> Reporter: Jan Ondrusek
> Fix For: 4.5.3, 5.0 Alpha2
>
>
> The original issue is described in this thread
> http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201309.mbox/%[email protected]%3E
> Copying relevant part:
> > AbstractConnPool class, which CPool is based upon, provides #enumLeased
> > method that can be used to enumerate leased connections and optionally
> > close some or all of them. Truth to be told, I simply forgot to add a
> > corresponding method to PoolingHttpClientConnectionManager.
> >
> > Please raise a change request in JIRA for this issue. For the time being
> > you will have to resort to reflection in order to get hold of the 'pool'
> > instance variable and cast it to AbstractConnPool.
> There is a PoolingHttpClientConnectionManager#closeExpiredConnections method,
> which is used by IdleConnectionEvictor to handle expired connections.
> Could a similar method be added for leased connections as well?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
