Make failure to create an eventfd non-fatal

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • Service Arch 2019-03-25
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After introducing the linux baton more widely (on each client, on creation, rather than during an ARS dispatch), users are more likely to encounter that condition, and we can handle it more gracefully.

      By changing the failure to create an eventfd into a throwing exception, we'll cause new client object creation to throw, which will cause us to close the incoming client socket.

            Assignee:
            Mira Carey
            Reporter:
            Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: