Thanks a lot for the hint Chuck,
I think I know what happened, tomcat ran out of heap so the JVM tried
to agressivly free some space and wasted some minutes. When there was
enough free space to complete the request, the connection already had
timed out.
Its just a thought but seems quite realisti
> From: Clemens Eisserer [mailto:[EMAIL PROTECTED]
> Subject: Suddenly server only throws ClientAbortException :-/
>
> Tomcat suddenly throws at every request a ClientAbortException, like
> the following:
>
> ERROR 2006-10-30 07:21:17,736 - ClientAbortException:
> java.net.SocketException: Conne
Hi again,
Could this have something todo with missing free heap space? Some
lines later in my log-file I see a OufOfMemoryException happen,
although between there have been some sucessful requests.
lg Clemens
2006/11/3, Clemens Eisserer <[EMAIL PROTECTED]>:
Hello,
One of our users is using To
