Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Mon, 27 May 2013 16:42:20 +0000 (UTC)
From: "Ignat Alexeyenko (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12649581.1369669224111.26700.1369672940084@arcas>
In-Reply-To: <JIRA.12649581.1369669224111@arcas>
References: <JIRA.12649581.1369669224111@arcas>
Subject: [jira] [Commented] (HTTPCORE-341) As a developer I want NIO Pool to
 close 'slow' http requests automatically
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ignat Alexeyenko commented on HTTPCORE-341:
-------------------------------------------

Hi Oleg, 

Yes, I'd like to support the request deadline. From what I saw - AbstractNIOConnPool already handles timeout for leasedRequests that are not yet executed. That's why I think it could also manage the 'slow' connections. If this is not a case it could be implemented in AbstractNIOConnPool, could you provide any tips on how to free the pool from slow connections?

Thanks for cooperation and fast replies!

--
Cheers,
Ignat.
                
> 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