I'd say that you've started too many threads; when there are no more threads
available in the thread pool, Tomcat refuses connections.
You should increase the number of threads in the pool. Sadly, I don't know
how to do that; and would like to know :)
Cheers,
Alex.
Markus Ebersberger wrote:
> Hi,
>
> I'm testing a servlet-application that is using Tomcat v 3.1
> (standalone,
> without Apache) running on Win2K Workstation.
> The tool I'm using for testing starts a (configurable) number of
> threads,
> each of which connects to the server, sends a HTTP-request and waits for
> the response. It runs on the same machine as the server.
> When I start many threads simultaneously, the server sometimes refuses
> connections (I get a ConnectException on client side).
> The tomcat logfile shows nothing unusual.
> Does someone know a possible reason for this behaviour or even a
> solution ?
> (I suspect that the "connection request queue" (I don't know the correct
> term ) of the operating system is too short, but where can i adjust
> this ?)
>
> Thanks in advance,
> Markus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
