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

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated JGRP-1659:
--------------------------------

    Attachment: expiration-test.zip


build first:
mvn clean install -Dmaven.test.skip.exec=true

Thne run the tests:

It generates random payloads of different sizes according to a distribution.
At client, the actual payload size ranges from 10k to 2mb.  However, this test only simulates btwn 10 bytes to 50k bytes - and locking still occurs.

Do not run unit tests - those tests are for other things ;)  To run the actual test, do:

mvn -e exec:exec -Dnode=n  // where n is the node number 1 to 4 etc.

What I do is open 3 terminals/tabs/screens, whichever you prefer, each run:
mvn -e exec:exec -Dnode=1
mvn -e exec:exec -Dnode=2
mvn -e exec:exec -Dnode=3
...

It'll prompt you to press a key when ready.  When you confirm cluster has formed, press any key to continue on all the nodes.


(tests courtesy to [~saturnism]])
                
> deadlock in MFC with default configureation
> -------------------------------------------
>
>                 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
>         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