Hi,

we are using TC 3.2.2 (upgrade to 3.2.3 soon to follow) in
a production environment with medium traffic and standalone
mode. The configuration in server.xml is identical to the
distribution, except for the modified port number and an

   <Parameter name="max_threads" value="500"/>

in the configuration of the HTTP connector. Other connectors
are not in use, except for shutdown (AJP12).

 From time to time it occurs, that TomCat is no more serving
requests. In the error log I find the message "thread pool
exhausted". The dropouts could be reduced by increasing the
thread pool size and by rebooting nightly. However, from
time to time the problem still occurs, although I am sure
that we never serve 500 concurrent connections.

My question is: How do I debug the problem? I would like
to insert appropriate log statements into the TomCat
source, that tell me when a new thread is created, when
its serving a request, when it finishs serving a request,
when its returned to or obtained from the pool in the
hope to find a responsible problem in some servlet or
whatever by analyzing thir output.

However, I am not sufficiently used to the TomCat source
to determine the appropriate locations for such logging
statements. Any help appreciated.


Thanks,

Jochen

Reply via email to