[jboss-jira] [JBoss JIRA] (JGRP-1659) deadlock in MFC with default configuration

[Ray Tsang (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790442#comment-12790442 ] 

Ray Tsang commented on JGRP-1659:
---------------------------------

RHEL 6.2 2.6.32-220.23.1.el6.x86_64

OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

                
> deadlock in MFC with default configuration
> ------------------------------------------
>
>                 Key: JGRP-1659
>                 URL: https://issues.jboss.org/browse/JGRP-1659
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.2.7
>            Reporter: Mircea Markus
>            Assignee: Bela Ban
>             Fix For: 3.4
>
>         Attachments: expiration-test.zip
>
>
> MFC.down does the following:
> {code:java}
>             credits.decrement(length, block_time); //A
>             if(needToSendCreditRequest()) //B
>                     sendCreditRequest(tuple.getVal1(), Math.min(max_credits)
> {code}
> A blocks forever even if the MFC.max_block_time is configured:
> {code:xml}
> <MFC max_credits="200k" min_threshold="0.20" max_block_time="1"/>
> {code} 
> This happens at the same time on the whole cluster. B never gets invoked, so both wake up conditions( credits received or timeout) for credits.decrement are never satisfied resulting in the whole cluster to freeze.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira