[
https://issues.apache.org/jira/browse/HTTPCLIENT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552464
]
Roland Weber commented on HTTPCLIENT-677:
-----------------------------------------
Yes, I was hoping for java.util.concurrent too. Lock and Condition seem to fit
the problem:
http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/locks/Condition.html
http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/locks/Lock.html
One lock for the pool, one condition for each thread. I'll have to dig through
the JavaDocs.
cheers,
Roland
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
