Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5113

Generalize/centralize treatment of broken pipe / ClientAbortException / etc

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Neutral Neutral
    • None
    • None
    • core
    • None

      As described in MAGNOLIA-5112, we have a few places where we treat {{IOException}}s and basically just ignore them because they might be a sign for a client abort or broken pipe; we can't really do anything else because we don't want to be container-specific.

      A possible improvement, however, would be to centralize this behavior - a possible solution to that is described and discussed in MAGNOLIA-3595.
      This would allow for something a little smarter/safer; we don't want to replicate this code everywhere: other IOException should not be ignored.

        Acceptance criteria

              Unassigned Unassigned
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD