I wondering if no one has come across this problem or is it just to broad of
an exception?
John
-Original Message-
From: O'Neill, John
Sent: Thursday, February 06, 2003 9:28 AM
To: '[EMAIL PROTECTED]'
Subject: Socket Exceptions
I'm trying to get an idea of the root cause for this
I have seen this in cases you described (pushing stop, or closing the
browser) after the servlet has started sending output. Obviously, users
never see it (they pressed stop or closed the browser), but it does show
up in my error log. I finally added code to catch and suppress it in my
servlet.
