No, AFAIK it is because the IOException is handled differently from the
IllegalStateException:
The IllegalStateException causes a recursive error handling trap to occur
that gradually fills up the stack and blows the system.
Because you've got a number of requests happening it hides the fact that
IllegalStateException is happening repeatedly off the handling of one
(closed) request. IMHO!
david
----- Original Message -----
From: "Robert Douglass" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 9:19 PM
Subject: RE: java.lan.OutOfMemoryError
> I changed the JDK back to 1.3.1 (which is what my class files were
compiled
> with) and the error message:
> 2002-03-22 22:17:32 - Ctx( /RobertDouglass ): IOException in: R( /Robert
> + /img/Beetle4.gif + null) Connection aborted by peer: socket write err
>
> is still there every time it loads an image, but I cannot get the
> java.lang.OutOfMemoryError.
>
> Whether this is because more resources are available on my system, I don't
> know.
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
