hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manikandan Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HTTPCLIENT-1729) Evicting Stale connections from the connection pool
Date Fri, 04 Mar 2016 22:01:40 GMT
Manikandan Subramanian created HTTPCLIENT-1729:

             Summary: Evicting Stale connections from the connection pool
                 Key: HTTPCLIENT-1729
                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1729
             Project: HttpComponents HttpClient
          Issue Type: Bug
    Affects Versions: 4.5.2
            Reporter: Manikandan Subramanian
            Priority: Minor

This is not a bug. But more of a guidance needed here.

The below documentation suggests


to use a separate monitor thread that calls closeExpiredConnections() method for stale connection

Is this still applicable for 4.5.2 version as well ? I am looking at source code PoolingHttpClientConnectionManager#closeExpiredConnections
which in turn calls the pool#closeExpired.

The closeExpired method checks only the expiration of the connections. However there seems
to be no check on whether the connection is stale.

Should we still handle stale connections checks when using Apache HttpClient 4.5 ? What is
the guidance here ?

Minor possible documentation issue 


The above java doc claims that the default timeout that is used before a stale connection
check is performed is 5000 ms. However the source code is setting the value to 2000ms. Please
correct me if I am wrong. 

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