On 25/07/2022 10:55, John English wrote:
On 25/07/2022 04:52, Greg Wilkins wrote:
How was the exception logged?
Normally we try to suppress such IO exceptions, as they can happen at
any time if a client closes the connection (goes into a tunnel, closes
laptop lid etc.). But perhaps this one has slipped through.
I catch IOException in my webapp and ignore, but this one was from
Jetty, not my webapp, so it hit my if-all-else-fails handler which sends
me an email message when anything unhandled happens:
<error-page>
<exception-type>java.lang.Exception</exception-type>
<location>/error</location>
</error-page>
Incidentally, I have to handle IOException in my webapp because I quite
often used to get "unexpected EOF" type errors reported by email. But
since the IOException is normally wrapped inside a Jetty-specific
exception, I have to deal with it as follows to avoid Jetty-specific
code in my webapp:
catch (Throwable e) {
if (e instanceof IOException ||
e.getCause() instanceof IOException) {
...
}
}
--
John English
--
This email has been checked for viruses by AVG.
https://www.avg.com
_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
