uCosminexus Application Server, Web Container Functionality Guide

[Contents][Glossary][Index][Back][Next]

2.13.1 Types and number of the threads created

The following table describes the threads created by a Web container:

Table 2-43 Threads created by a Web container

Classification of threads Reference
Threads for the simple Web server of a Web container (1)
Threads for using the Web server integration functionality#1 (2)
Threads for using the in-process HTTP server#2 (3)
Threads for the Web application (4)
Threads for the context used for management (5)
Threads for monitoring the timeout when sending a response (6)

#1
Threads created when the Web server integration functionality is used.

#2
Threads created when the in-process HTTP server is used.

Organization of this subsection
(1) Threads for the simple Web server of a Web container (mandatory)
(2) Threads for using the Web server integration functionality
(3) Threads for using the in-process HTTP server
(4) Threads for the Web application
(5) Threads for the context used for management
(6) Threads for monitoring the timeout when sending a response

(1) Threads for the simple Web server of a Web container (mandatory)

The types and the number of threads created by the Web container for the simple Web server are explained below:

Threads created
Web container creates the threads for receiving the requests for establishing TCP connection, as well as threads for processing the received requests.

Number of threads
One thread is created for receiving the requests for establishing TCP connection. A minimum of five threads and maximum 100 threads are created for processing the requests received by the simple Web server.
During invocation, five threads are created for processing the requests. When the number of concurrently executing threads exceeds the number of already invoked threads, up to 100 threads are created.

Always use the simple Web server of the Web container.

(2) Threads for using the Web server integration functionality

The types and the number of threads created by the Web container for integrating with the Web server are explained below:

Threads created
Web container creates the threads for receiving requests from the redirector for establishing a connection, as well as threads for processing the requests received from the redirector.

Number of threads
One thread is created for receiving requests from the redirector for establishing a connection. Threads equal to the number of connections between the Web server and the Web container are created for processing the requests received from the redirector
During invocation, threads equal to the number specified in the webserver.connector.ajp13.max_threads key of usrconf.properties are created for processing the requests received from the redirector (default value of webserver.connector.ajp13.max_threads key is 10).

(3) Threads for using the in-process HTTP server

The types and the number of threads created by the Web container for the in-process HTTP server are explained below:

Threads created
The Web container creates the threads for processing the requests and the threads for monitoring the number of request processing threads.

Number of threads
The threads equal to the number of connections from the Web client or proxy server are created for processing the requests. The request processing threads equal to the number specified in the webserver.connector.inprocess_http.init_threads key of usrconf.properties are created when the J2EE server starts (default value of webserver.connector.inprocess_http.init_threads key is 10). When the number of concurrently executing threads exceeds the number of threads created during the invocation of the J2EE server, the request processing threads are created with the maximum number of connections from the Web client as the upper limit (default value of webserver.connector.inprocess_http.max_connections key is 100).
Furthermore, one thread is created for monitoring the number of request processing threads.

(4) Threads for the Web application

In each Web application, Web container creates threads for monitoring the valid time period of a session. A minimum of one thread and maximum three threads are created.

(5) Threads for the context used for management

Web container creates two threads for generating two contexts for management.

(6) Threads for monitoring the timeout when sending a response

If you enable the timeout when sending a response, Web container creates one thread for monitoring the send timeout.