On 12/6/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
so what you fix was nothing.
You still get swamped in exceptions on jetty for OSX and now also others
that do throw
the right socket exception are getting swamped with exceptions.
No, because I log a warning exluding the exception. But fine
so what you fix was nothing.
You still get swamped in exceptions on jetty for OSX and now also others
that do throw
the right socket exception are getting swamped with exceptions.
As i said. sending a status code doesn't make any sense. because the
response is already broken.
johan
On 12/6/06
It just didn't work. It didn't work for Jetty on Linux and OSX, but it
did for Jetty on Windows. Jetty throws an EofException, which extends
IOException. And we were getting swamped with exceptions. That piece
of code only caught a number of cases it seems. I see the fix isn't
correct either, so w
I am not happy with this change.
We should try to ignore the client abort or connection reset as much as we
can
Now the log will be completely filled with exceptions you don't have
anything.
Sending a http response error/status code is by the way not possible then
because the connection is reset
