Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-3044

SSE first message comes in second

    XMLWordPrintable

Details

    • Hide

      Run the test to reproduce RESTEASY-3033, it can be found at https://github.com/resteasy/resteasy/pull/2938 .

      If you take in the fix for the deadlock, it will almost always fail with a trace like this:

       Wrong message order in run 6 [msg-1, msg-0, msg-2, msg-3, msg-4, msg-5, msg-6, msg-7, msg-8, msg-9, msg-10, msg-11, msg-12, msg-13, msg-14, msg-15, msg-16, msg-17, msg-18, msg-19, msg-20, msg-21, msg-22, msg-23, msg-24, msg-25, msg-26, msg-27, msg-28, msg-29, msg-30, msg-31, msg-32, msg-33, msg-34, msg-35, msg-36, msg-37, msg-38, msg-39, msg-40, msg-41, msg-42, last-msg-43]

      This problem happens in around 20% of the requests, the tests executes 100 requests.

      Show
      Run the test to reproduce RESTEASY-3033 , it can be found at https://github.com/resteasy/resteasy/pull/2938 . If you take in the fix for the deadlock , it will almost always fail with a trace like this: Wrong message order in run 6 [msg-1, msg-0, msg-2, msg-3, msg-4, msg-5, msg-6, msg-7, msg-8, msg-9, msg-10, msg-11, msg-12, msg-13, msg-14, msg-15, msg-16, msg-17, msg-18, msg-19, msg-20, msg-21, msg-22, msg-23, msg-24, msg-25, msg-26, msg-27, msg-28, msg-29, msg-30, msg-31, msg-32, msg-33, msg-34, msg-35, msg-36, msg-37, msg-38, msg-39, msg-40, msg-41, msg-42, last-msg-43] This problem happens in around 20% of the requests, the tests executes 100 requests.

    Description

      When SSE events are quickly send from the server it is possible that the first event send on the server comes in second on the client side.  So the event order is somehow messed up.

      We saw this only happen with the first event.  For all other events the order is correct.

      With the test to reproduce RESTEASY-3033 we found 2 other issues, this is one of them, the other is RESTEASY-3045.

       

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-15801 Upgrade RESTEasy to 4.7.4.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-3033 Deadlock while sending sse events when first event is not yet send

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              jperkins-rhn James Perkins
              steven.aerts Steven Aerts (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: