Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-3811

Add a CancellableQueue to make close methods safer

Details

    • Bug
    • Status: Resolved
    • P3
    • Resolution: Fixed
    • None
    • 2.35.0
    • runner-core

    Description

      There are multiple locations in which, on a call to close within some portability service, we wish to close all of our outstanding clients. However, the call to close can be interleaved with calls to the method which creates a new client. Without having an explicit thread-safe signal from the collection of pending clients, there's no way to ensure that all of the clients for a service are closed when that service is closed. 

       

      As a result, some clients are only terminated by the forceful termination of the server, killing the connection.

      Attachments

        Issue Links

          Activity

            People

              lcwik Luke Cwik
              tgroh Thomas Groh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 5h 10m
                  5h 10m