hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Ondrusek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1760) PoolingHttpClientConnectionManager has no option to close long leased connections
Date Thu, 04 Aug 2016 17:39:20 GMT
Jan Ondrusek created HTTPCLIENT-1760:

             Summary: PoolingHttpClientConnectionManager has no option to close long leased
                 Key: HTTPCLIENT-1760
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1760
             Project: HttpComponents HttpClient
          Issue Type: Bug
          Components: HttpClient
    Affects Versions: 4.5, 4.4.1
            Reporter: Jan Ondrusek

The original issue is described in this thread http://mail-archives.apache.org/mod_mbox/hc-httpclient-users/201309.mbox/%3C5239A981.6040405@europages.com%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

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message