You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2017/01/28 09:55:24 UTC

[jira] [Resolved] (HTTPCORE-443) Overflow in Connection TTL

     [ https://issues.apache.org/jira/browse/HTTPCORE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCORE-443.
----------------------------------------
    Resolution: Fixed

> Overflow in Connection TTL
> --------------------------
>
>                 Key: HTTPCORE-443
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-443
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore, HttpCore NIO
>    Affects Versions: 4.4.6
>            Reporter: Andrew Shore
>            Priority: Minor
>              Labels: easyfix, performance
>             Fix For: 4.4.7, 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 environments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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