[
https://issues.apache.org/jira/browse/HTTPCLIENT-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579632#action_12579632
]
Oleg Kalnichevski commented on HTTPCLIENT-734:
----------------------------------------------
Sam,
This is a tricky one.
I kind of dislike the idea of having to interrupt the thread in order to
unblock the connection manager. Besides, not all connection manager
implementation would necessarily block on connection allocation. So, I am
thinking if a better solution could be to return an optional handle object,
which could be used to unblock the connection manager without interrupting the
thread.
Does this make any sense to you? If not, i'll commit your patch as is
Oleg
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
