[jira] Resolved: (WICKET-155) Extend cases where the exception can be ignored due to an aborted request

["Eelco Hillenius (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius resolved WICKET-155.
------------------------------------

    Resolution: Fixed

Been open long enough now. Seems to work fine for most people.

> Extend cases where the exception can be ignored due to an aborted request
> -------------------------------------------------------------------------
>
>                 Key: WICKET-155
>                 URL: https://issues.apache.org/jira/browse/WICKET-155
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.2.4, 1.3, 2.0
>            Reporter: Eelco Hillenius
>         Assigned To: Johan Compagner
>
> We should either find more specific catches in Resource#respond or come up with some other way to ensure we can recognize a client abortion. For instance, Jetty 6 on unix-like platforms (tested here on OpenBSD/ OSX) throws EofExceptions which extend IOExceptions and thus are not marked as ignorable. The problem then is that a stack trace will be printed in ComponentResourceRequestTarget, and as many production systems will have some trigger installed that sends an error message/ SMS/ ... that can be quite annoying.
> Can't we instead of looking at the exception somehow look at the request/ response itself to figure out that a request was aborted? If that is possible, that seems like a much more robust way of solving this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.