[CAUSEWAY-2071] [WON'T FIX] Backport suppression of "client connection abort" errors from v2

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Fix Version/s: v1 maintenance
• Assignee: Unassigned
• Reporter: Daniel Keir Haywood
• Created: 04/Jan/19 11:57
• Updated: 17/May/19 16:18
• Resolved: 17/May/19 16:18

Description

In ResourceCachingFilter.
 

    ...

    // try to suppress java.io.IOException of kind 'client connection abort'
    // 1) the TCP protocol (by design) does not provide a means to check, whether a
    //    connection has been closed by the client
    // 2) the exception thrown and the exception message text are specific to the
    //    servlet-engine implementation, so we can only guess here
    try {
        chain.doFilter(servletRequest, servletResponse);    
    } catch (IOException e) {
        FluentException.of(e)
        .suppressIf(this::isConnectionAbortException);
    }
}

// -- HELPER

private boolean isConnectionAbortException(IOException e) {
    // tomcat 9
    if(e.getMessage().contains("An established connection was aborted by the software in your host machine")) {
        return true;
    }
    // payara 4
    if(e.getMessage().contains("Connection is closed")) {
        return true;
    }

    return false;
}