hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1835) evictExpiredConnections does not work as intended
Date Fri, 24 Mar 2017 15:32:41 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940542#comment-15940542

ASF GitHub Bot commented on HTTPCLIENT-1835:

Github user theangrydev commented on the issue:


> evictExpiredConnections does not work as intended
> -------------------------------------------------
>                 Key: HTTPCLIENT-1835
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1835
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (async), HttpClient (classic)
>    Affects Versions: 4.5.4, 5.0 Alpha3
>            Reporter: Liam Williams
>             Fix For: 4.5.4, 4.6 Alpha1, 5.0 Alpha2
> HttpClientBuilder and HttpAsyncClientBuilder have an evictExpiredConnections method that
is supposed to allow configuring a client that will evict expired connections.
> When evictExpiredConnections is used alongside evictIdleConnections, everything is fine.
> However, if evictExpiredConnections is used without evictIdleConnections, currently the
builder will default to also providing the evictIdleConnections behaviour (defaulting to evicting
idle connections after 10 seconds).
> The correct behaviour in this case is to only provide the evictExpiredConnections behaviour
and not the evictIdleConnections behaviour.

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