The Web Container provides a pool of threads that can be
configured as shown below. When Application Server V5 releases start the
Web Container, threads are not started until they are needed. This
behavior is different than the V4.0 Web Container. The V4.0 Web Container
will start the number of threads that are specified as the minimum size at
start. The V4.0 Web Container will never have less than the configured
minimum number of threads for serving client requests.
In V5 releases, the Web Container behaves slightly different. It will
only start a thread when necessary. Therefore it may have fewer threads
than specified by the minimum size. In addition, it will not destroy a
thread until it creates more then the configured minimum size.
For example, if the minimum size configured is 10 and the maximum size
configured is 50, the threads in the Web Container for serving JSP™ and
servlets at start will be zero until a servlet or JSP is requested. Once a
servlet is requested, there will be one Web Container thread for serving
requests until there are multiple simultaneous requests. At that time, the
Web Container will start threads as needed to satisfy the simultaneous
requests. Once the number of threads reaches 10 or more, there will be no
less than 10 threads for the life of the Web Container. If requests are
made requiring 15 threads, there will be 15 threads in the thread pool. If
the load subsides for a period of time, the Web Container will destroy up
to 5 threads and 10 will remain.

|