[jboss-jira] [JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks

[Richard Achmatowicz (JIRA)]

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

Richard Achmatowicz commented on JGRP-1759:
-------------------------------------------

The debugging output above clearly shows the correct rule being loaded, processed and called.

I can't say for sure where/why the program is being deadlocked; I guess the next step is to run it locally on that machine (the tests are run via Jenkins) and create a thread dump. But, as you know, whenever you use a rendezvous with no timeout, the possibility for deadlock is there.

I was going to suggest to Andrew to create a version of rendezvous which if all threads do not arrive after a specified timeout, performs the thread dump itself as well as listing the threads which did/did not make it to the rendezvous point. That information would have been helpful here.
                
> BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
> ----------------------------------------------------------------
>
>                 Key: JGRP-1759
>                 URL: https://issues.jboss.org/browse/JGRP-1759
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.5
>         Environment: Windows 2008, x86_64
>            Reporter: Richard Achmatowicz
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.5
>
>
> Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang.
> The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks.
> .

--
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