You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Andi Huber (JIRA)" <ji...@apache.org> on 2018/06/04 07:00:04 UTC
[jira] [Closed] (ISIS-1961) ResourceCachingFilter: Suppress 'client
connection abort' exceptions.
[ https://issues.apache.org/jira/browse/ISIS-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andi Huber closed ISIS-1961.
----------------------------
Resolution: Works for Me
Fell free to add a suppression requests for your specific servlet-engines. By now, works for me.
> ResourceCachingFilter: Suppress 'client connection abort' exceptions.
> ---------------------------------------------------------------------
>
> Key: ISIS-1961
> URL: https://issues.apache.org/jira/browse/ISIS-1961
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Minor
> Fix For: 2.0.0-M1
>
>
> I think with Firefox's latest Quantum engine I started to see frequent IOExceptions caused by 'client connection abort'.
> So we might try to suppress java.io.IOException of kind 'An established connection was aborted by the software in your host machine'
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)