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] [Resolved] (HTTPCORE-315) HttpAsyncRequester leaks a connection if a request is cancelled before the connection is established
Date Wed, 03 Oct 2012 14:48:07 GMT

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

Oleg Kalnichevski resolved HTTPCORE-315.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.2.3

Hi Scott,
Many thanks for a detailed analysis of the problem and a quality patch. Patch committed to
both SVN trunk and 4.2.x branch.

Oleg
                
> HttpAsyncRequester leaks a connection if a request is cancelled before the connection
is established
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-315
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-315
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.2.2
>            Reporter: Scott Stanton
>             Fix For: 4.2.3
>
>         Attachments: HTTPCORE-315.patch
>
>
> When using HttpAsyncRequester in combination with a BasicNIOConnPool, if the future returned
from execute() is cancelled before the connection is established, then the connection will
be leaked after it connects (added to the leased list after the cancelled() callbacks are
invoked).  The sequence that leads to this is:
> * AbstractNIOConnPool.requestCompleted() calls RouteSpecificPool.completed() which ultimately
calls HttpAsyncRequester.completed()
> * HttpAsyncRequester.completed() detects that the requestFuture is done, so it attempts
to release the pool entry
> * The pool entry hasn't been added to the leased list yet, so the release has no effect
and the connection is not added to the available list
> * After the completed callback returns to requestCompleted(), the connection is added
to the leased list.
> At this point, no thread is expecting to do anything further with the connection, so
it is effectively lost and consuming a pool slot.
> I think the correct remedy is to ensure that the connection is added to the global leased
list as well as the route specific leased list before the completed() callback is invoked.
 This should ensure that the connection is properly cleaned up.

--
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