hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCORE-341) As a developer I want NIO Pool to close 'slow' http requests automatically
Date Wed, 29 May 2013 09:33:20 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669116#comment-13669116
] 

Oleg Kalnichevski commented on HTTPCORE-341:
--------------------------------------------

Ignat
I think what we could do as an interim solution until support for request deadlines is implemented
at the I/O reactor level is to expose a method to enumerate leased connections through the
connection manager APIs. Connection manager implementations would simply delegate execution
of this method to the underling pool (AbstractNIOConnPool subclass). Both core and async components
would be affected. I do not  think there any reason for raising another JIRA, though.

Oleg
                
> As a developer I want NIO Pool to close 'slow' http requests automatically
> --------------------------------------------------------------------------
>
>                 Key: HTTPCORE-341
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-341
>             Project: HttpComponents HttpCore
>          Issue Type: New Feature
>    Affects Versions: 4.2.2, 4.3-beta3
>            Reporter: Ignat Alexeyenko
>            Priority: Critical
>              Labels: ha
>         Attachments: JRADEV-21355-httpcore-nio-process-slow-requests_patch.patch
>
>
> Currently the AbstractNIOConnPool is capable to handle timeouts for en-queued requests
(requests added in leasingRequests connection).
> What AbstractNIOConnPool - deal with slow connections, that already are open and being
executed. Slow connections are connections that are not completed withing some request processing
timeout.
> Example. Consider a specific case, when a remote server holds a connection open, but
transmits information slowly (e.g. 8 bytes in each 100ms). In application under the high load
it means that we would stuck with no free connections to process new requests for a long period
of time.
> In such cases, as a developer I want to specify time in which we would close current
open connection, even if it is already processing the data.

--
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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message