I assume that your web app was dealing with a backend database. In that
case, it is quite possible that your JDBC data source is running out of
connections. So the timeout is not necessarily caused by the servlet,
but by the connection pool. One option is to increase the number of
connections in
It is the Connector element which you need to adjust, i.e., up the
maxThreads value.
> -Original Message-
> From: foo shyn [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 24, 2006 6:05 AM
> To: users@tomcat.apache.org
> Subject: Tomcat servlet load handling
>
>
> Hi,
>
>
