http://jira.codehaus.org/browse/JETTY-1460
There is a difference between jetty-6 and jetty-7/8 with regards the UncheckedPrintWriter. In jetty-6, any exception caused by the IO was suppressed. In jetty-7, the UncheckedPrintWriter is used and defaults to throwing the exception as a runtime exception.
These are the relevant issues:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318551
http://jira.codehaus.org/browse/JETTY-1086
I still believe that this log message is caused by a client (or the network or the server's operating system) closing the connection to the client when output is still being written to it.
I will look at why we don't have the ability to turn off the throwing of these runtime IOExceptions (like we do if we are using the UncheckedPrintWriter for the IncludableGzipFilter).
In the meanwhile you may want to set up some custom error pages for the webapp.
====
org.eclipse.jetty.io.EofException
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host