I get these when someone is hitting against me with a web-browser, then
hits stop, or goes to another page before the servlet or WOA returns the
page. There's a socket exception when you try to write to the
response's open socket (upon flushing a response object's buffer, I
presume).
It's actually a real service, as it keeps you from going through
needless extra work if the client has already given up.
Regards,
Christian.
> -----Original Message-----
> From: Anders Peterson [mailto:anders_peterso..ptimatika.se]
> Sent: Monday, February 17, 2003 11:07 AM
> To: woproject-de..bjectstyle.org
> Subject: java.net.SocketException
>
>
> Hi all,
>
> Have you seen an Exception like this before?
>
> [2003-02-06 18:25:32 CET] <WorkerThread8> <WOWorkerThread id=8
> socket=Socket[addr=vssto-dc1.vs.x-change.se/
> 192.168.10.1,port=3722,localport=2001]> Exception while sending
> response: java.net.SocketException: Connection aborted by
> peer: socket
> write error
>
> I assume you have. At least something similar. My problem is that I
> can't figure out where it comes from. It's not from one of "my
> threads". I am unable to catch these exceptions, and the log entry
> (which is written by some API code) appears right in the middle of
> everything and anything.
>
> Under heavier load the application starts behaving badly,
> although it
> does work, but will eventually become "unresponsive" and
> difficult to
> kill. (WO5.1 on Win2k)
>
> I believe that these Exceptions appear always, but they are
> much more
> frequent under heavier load.
>
> One would guess there is something wrong with our network,
> but this is
> the only problem we've seen.
>
> What specific part of the WO application could be throwing this
> exception?
>
> /Anders
>
>
This archive was generated by hypermail 2.0.0 : Mon Feb 17 2003 - 12:08:25 EST