One solution would be to update to 3.2.3 - if I remember corectly this has
been fixed.
Costin
On Wed, 8 Aug 2001, Wiedmann, Jochen wrote:
>
> Hi,
>
> I have just posted bug #3033 to nagoya, about a bug in the
> TCPPoolConnector. When running TomCat in standalone mode,
> after some time I notice the message
>
> ThreadPool: Pool exhausted with 100 threads.
>
> over and over again in the error log file. In practice
> this causes TomCat to be out of order.
>
> The problem can be demonstrated with the attached simple
> servlet. The servlet has a main() method, so that it can
> call itself from the command line. It spawns 10 threads,
> which keep calling the servlet in a never ending loop.
> Exceptions in both client and server are forced. After
> some minutes you will notice the "Pool exhausted" message
> in a default TomCat configuration, although the number
> of clients is 10 and the number of threads is 100.
>
> Any suggestions welcome,
>
>
> Jochen
>
>
