[
https://issues.apache.org/jira/browse/HTTPCLIENT-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552447
]
Oleg Kalnichevski commented on HTTPCLIENT-677:
----------------------------------------------
> - release lock on the object (?)
> - acquire a new lock on the pool (?)
I think granular lock management should be relatively simple since we have an
option of using java.util.concurrent. CountDownLatch may be the right thing to
use in this situation.
http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/CountDownLatch.html
Alternatively, this may be the right moment to evaluate Commons Pool or some
other external pooling library and see if that would make our life somewhat
simpler.
Oleg
> 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]
