[HTTPCLIENT-1760] PoolingHttpClientConnectionManager has no option to close long leased connections

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.4.1, 4.5
• Fix Version/s: 4.5.3, 5.0 Alpha2
• Component/s: HttpClient (classic)
• External issue URL: http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201309.mbox/[e-mail]%3E
• Assignee: Unassigned
• Reporter: Jan Ondrusek
• Created: 04/Aug/16 17:39
• Updated: 13/Aug/16 15:32
• Resolved: 13/Aug/16 15:32

Description

The original issue is described in this thread http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201309.mbox/[e-mail]%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?