Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5904

A deadlock can result if an EJB is being passivated at the same time an invocation made

    XMLWordPrintable

Details

    Description

      As seen in EJBClientDescriptorTestCase.testClientInvocationTimeout

      This can be reproduced locally by adding a loop around the final invocations in the test:

      for (int i = 0; i < 1000; ++i) {
            
  Assert.assertEquals("bar", remote1.getManagedBeanMessage());

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

      Attachments

        Activity

          Public project attachment banner

            context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
            current Project key: WFLY

            People

              pferraro@redhat.com Paul Ferraro
              sdouglas1@redhat.com Stuart Douglas
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: