[MAGNOLIA-5113] Generalize/centralize treatment of broken pipe / ClientAbortException / etc Created: 13/Jun/13  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLCACHE-48 Cache filter should rethrow exception... Closed
is related to MAGNOLIA-3595 Add an exception handler for filters. Closed
is related to MAGNOLIA-3566 Cache filter should ignore ClientAbor... Closed
is related to MAGNOLIA-5112 Responses served from cache can throw... Closed
is related to MGNLIMG-162 Ignore ClientAbortExceptions (broken ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

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.


Generated at Mon Feb 12 04:02:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.