but my server.xml as below, shows there is enough available threads. And
only 10 threads are attacking.
On Tue, 11 Jun 2002 09:33:55 +0530
Anand Bashyam Narasimhan <[EMAIL PROTECTED]> wrote:
> Typically the error that you are getting on the server side "connection
> reset by peer" happens whe
Typically the error that you are getting on the server side "connection
reset by peer" happens when a connection to the servlet is open and while
the request is being processed the stream to which the response is written
back is closed abruptly. You can easily replicate this with a simple
servlet,
it cause by a bug in
org/apache/tomcat/code/BufferedServletOutputStream.java
there is a cicular buffer where it set to 8k, when the html file which have
included files which size is
more then 8k , the above message will occur.
the cicular buffer was not reset after commit.
Below is the sou
The client (most notably, the browser) closed the socket. Maybe the user hit
the "Stop" button. Maybe the browser crashed. You can pretty much ignore
this, however you must be aware that writing to servlet's output stream can
result in this exception at any time (as users are free to hit "Stop" at
