[
http://jira.jboss.com/jira/browse/JBCOMMON-15?page=comments#action_12357562 ]
Ron Sigal commented on JBCOMMON-15:
-----------------------------------
I apologize if I inadvertently reopened an old issue. The description of the race
condition solved by MinPooledExecutor and the description of a supposed deadlock given in
http://altair.cs.oswego.edu/pipermail/concurrency-interest/2004-September...
seemed sufficiently different for me to think they were different problems. E.g., the
race solved by MinPooledExecutor assumes an unused thread, and the other problem starts
with the assumption that all threads are in use. Moreover, in his reply Doug Lea seems to
accept the deadlock description. However, I admit that I didn't look at the code to
see if the underlying problems could be related. In any case, thanks for responding.
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
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira