[
https://issues.apache.org/jira/browse/HTTPCORE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski moved HTTPCLIENT-1808 to HTTPCORE-443:
--------------------------------------------------------
Fix Version/s: (was: 5.0 Alpha3)
(was: 4.5.4)
5.0-alpha3
4.4.7
Affects Version/s: (was: 4.5.3)
4.4.6
Component/s: (was: HttpClient (classic))
HttpCore NIO
HttpCore
Workflow: classic default workflow (was: Default workflow,
editable Closed status)
Key: HTTPCORE-443 (was: HTTPCLIENT-1808)
Project: HttpComponents HttpCore (was: HttpComponents HttpClient)
> 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: [email protected]
For additional commands, e-mail: [email protected]
