hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Shore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1808) Overflow in Connection TTL
Date Thu, 26 Jan 2017 17:46:24 GMT

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

Andrew Shore commented on HTTPCLIENT-1808:

Sure thing. Is https://github.com/apache/httpcore/tree/4.4.x the best thing to fork and apply
my changes?

> Overflow in Connection TTL
> --------------------------
>                 Key: HTTPCLIENT-1808
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1808
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.3
>            Reporter: Andrew Shore
>            Priority: Minor
>              Labels: easyfix, performance
>             Fix For: 4.5.4, 5.0 Alpha3
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> There is a possibility of an overflow at https://github.com/apache/httpcore/blob/4.4.x/httpcore/src/main/java/org/apache/http/pool/PoolEntry.java#L88
when calculating the validity deadline. When Long.MAX_VALUE (or values sufficiently close
to it) is used as the TTL it results in a negative validity deadline which causes every connection
to be single use. This is very surprising behavior and may not be immediately obvious in test

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