[
https://issues.apache.org/jira/browse/HTTPCORE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCORE-340:
---------------------------------------
Component/s: HttpCore NIO
Summary: AbstractNIOConnPool to support lease timeout (was: As a
developer I want to specify leaseTimeout separately to connection timeout)
Almost there. Would not it be better though to support lease timeout on per
request basis similarly to connect timeout? All it takes an extra #lease method
added to AbstractNIOConnPool.
Oleg
> AbstractNIOConnPool to support lease timeout
> --------------------------------------------
>
> Key: HTTPCORE-340
> URL: https://issues.apache.org/jira/browse/HTTPCORE-340
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Components: HttpCore NIO
> Affects Versions: 4.2.2, 4.3-beta2
> Reporter: Ignat Alexeyenko
> Priority: Critical
> Fix For: 4.3-beta3
>
> Attachments: JRADEV-21355-httpcore-nio-after-review_patch.patch,
> JRADEV-21355-httpcore-nio-refactored_patch.patch
>
>
> The component httpasyncclient (class PoolingClientAsyncConnectionManager)
> uses httpcompnents-core (class AbstractNIOConnPool).
> In specific cases - such as remote server has slow response time (or just do
> not respond anything for a while), there could be a scenario, when
> AbstractNIOConnPool deletes request from leasingRequests which are not yet
> started.
> As a developer I want to have ability to specify leaseTimeout which would
> control how long request would be kept in leasingRequests unit it would be
> deleted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
