]
Dimitris Andreadis updated JBCOMMON-15:
---------------------------------------
Fix Version/s: (was: 1.0.4.GA)
Unscheduling for now.
In BasicThreadPool allow the queue passed to MinPooledExecutor to be
configurable.
----------------------------------------------------------------------------------
Key: JBCOMMON-15
URL:
http://jira.jboss.com/jira/browse/JBCOMMON-15
Project: JBoss Common
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.GA
Reporter: Ron Sigal
Assigned To: Dimitris Andreadis
According to
http://altair.cs.oswego.edu/pipermail/concurrency-interest/2004-September...,
"in certain circumstances the combination of PooledExecutor with BoundedLinkedQueue
with a waitWhenBlocked policy can lead to deadlock."
A post in the Remoting forum,
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995334#...,
indicates that a deadlock has been detected in Remoting due to its use of BasicThreadPool.
In response, the blocking policy in Remoting has been changed from WAIT to RUN, though
WAIT would be preferable. The poster in
http://altair.cs.oswego.edu/pipermail/concurrency-interest/2004-September...
indicates that an alternative solution is to use BoundedBuffer in place of
BoundedLinkedQueue.
It would be useful, therefore, if a queue could be passed to the BasicThreadPool
constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: