You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Sam Berlin (JIRA)" <ji...@apache.org> on 2008/03/17 18:14:25 UTC
[jira] Updated: (HTTPCLIENT-734) request.abort() should interrupt
thread waiting for a connection
[ https://issues.apache.org/jira/browse/HTTPCLIENT-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Berlin updated HTTPCLIENT-734:
----------------------------------
Attachment: changes.txt
Attached is a patch + testcase (that previously failed, but now passes) for this. Basically the idea is that DefaultClientRequestDirector installs its own ConnectionReleaseTrigger and then sets further triggers through that. Its trigger will interrupt the thread if no trigger has been set by the time abort is called, and if a delegate trigger is set after abort was called, it immediately throws an IOX & clears the interrupted status.
> 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
> Components: HttpClient
> Affects Versions: 4.0 Alpha 2
> Reporter: Roland Weber
> Fix For: 4.0 Beta 1
>
> Attachments: changes.txt, 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