You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Roland Weber (JIRA)" <ji...@apache.org> on 2007/12/28 18:40:43 UTC

[jira] Reopened: (HTTPCLIENT-677) Connection pool uses Thread.interrupt()

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

Roland Weber reopened HTTPCLIENT-677:
-------------------------------------


Thread.interrupt() shouldn't be used during shutdown either.
Locks are not guaranteed to implement interrupts.

Use regular signal plus a shutdown flag to detect that case,
throw dedicated shutdown exception instead of InterruptedException.


> Connection pool uses Thread.interrupt()
> ---------------------------------------
>
>                 Key: HTTPCLIENT-677
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-677
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>    Affects Versions: 4.0 Alpha 1, 4.0 Alpha 2
>            Reporter: Roland Weber
>            Assignee: Roland Weber
>             Fix For: 4.0 Alpha 3
>
>
> The connection pool for TSCCM uses Thread.interrupt() to wake up waiting threads.
> This interferes with application interrupts.
> - expose InterruptedException in interface
> - change pool implementation to use wait/notify

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