[jboss-jira] [JBoss JIRA] Resolved: (JGRP-928) Deadlock with concurrent stack in FC if RPC response blocks
Bela Ban (JIRA)
jira-events at lists.jboss.org
Fri Mar 13 05:19:23 EDT 2009
[ https://jira.jboss.org/jira/browse/JGRP-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban resolved JGRP-928.
---------------------------
Resolution: Done
Made ignore_thread a ThreadLocal<Boolean>. False by default, on up(), the thread sets it to true (and to false when the up call returns). The down() method checks if it is set to true (if enabled) and doesn't block on credits if so.
> Deadlock with concurrent stack in FC if RPC response blocks
> -----------------------------------------------------------
>
> Key: JGRP-928
> URL: https://jira.jboss.org/jira/browse/JGRP-928
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.6.8
> Reporter: Brian Stansberry
> Assignee: Bela Ban
> Fix For: 2.6.9, 2.8
>
>
> JGroups 2.4 and earlier had a deadlock problem in FC if a thread carrying an RPC came back down the stack with a response and blocked for credits. This was fixed with JGRP-465. But with the concurrent stack that fix has broken; needs to be reinstated. The variable that tracks upgoing threads needs to be converted from a ref to a Thread to a Set<Thread>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list