Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.11.1, 2.12
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      UNICAST2_StressTest: annotate stressTest with @Test(invocationCount=20). Ca 10% of all runs fail.

      Show
      UNICAST2_StressTest: annotate stressTest with @Test(invocationCount=20). Ca 10% of all runs fail.

      Description

      Under stress, UNICAST2 can deliver messages in incorrect order. The reason is that in UNICAST2.handleDataReceived() 'processing' is set to false in the finally clause, no matter what. This can cause multiple threads to concurrently deliver messages for the same destination.

      SOLUTION: copy the code from NAKACK.handleMessage(), which does not set 'processing' to false in finally

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                belaban Bela Ban
                Reporter:
                belaban Bela Ban
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: