hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HTTPCLIENT-734) request.abort() should interrupt thread waiting for a connection
Date Sat, 26 Jan 2008 18:52:37 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562904#action_12562904

Roland Weber commented on HTTPCLIENT-734:

Hi Oleg,

that takes care of opening the connection. But it does not address the interval that a thread
spends in allocateConnection(). If we want to address that, we'll have to store a thread in
the AbortableHttpRequest and interrupt the thread if there is no ConnectionReleaseTrigger.
I'm not sure whether that is what we want, but it seems to be a sensible behavior from a user

Please go ahead and commit the patch, it already improves the behavior.


> request.abort() should interrupt thread waiting for a connection
> ----------------------------------------------------------------
>                 Key: HTTPCLIENT-734
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-734
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>    Affects Versions: 4.0 Alpha 2
>            Reporter: Roland Weber
>             Fix For: 4.0 Beta 1
>         Attachments: connabort.patch
> Calls to HttpRequestBase.abort() will not unblock a thread that is still waiting for
a connection and therefore has no ConnectionReleaseTrigger yet.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message