[jboss-jira] [JBoss JIRA] (WFLY-5904) A deadlock can result if an EJB is being passivated at the same time an invocation made

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-5904:
-------------------------------
    Affects Version/s: 10.0.0.Final


> A deadlock can result if an EJB is being passivated at the same time an invocation made
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-5904
>                 URL: https://issues.jboss.org/browse/WFLY-5904
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 10.0.0.Final
>            Reporter: Stuart Douglas
>            Assignee: Paul Ferraro
>         Attachments: passivationTestFailureDump.txt
>
>
> As seen in EJBClientDescriptorTestCase.testClientInvocationTimeout 
> This can be reproduced locally by adding a loop around the final invocations in the test:
> {code}
> for (int i = 0; i < 1000; ++i) {
            
>   Assert.assertEquals("bar", remote1.getManagedBeanMessage());

>   Assert.assertEquals("bar", remote2.getManagedBeanMessage());
        
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)