By controlling the number of connections and number of request processing threads from the Web client and by optimizing the number of request processing threads, you can constantly control the load on the J2EE server and maintain a stable and high throughput. For details on controlling the number of request processing threads, see 5.4 Controlling the number of request processing threads.

This section describes the controlling of the number of connections from the Web client.

The following table describes the organization of this section.

Table 5-4 Organization of this section (Controlling the number of connections from the Web client)

Category	Title	Reference
Description	Overview of controlling the number of connections from the Web client	5.3.1
Settings	Execution environment settings (J2EE server settings)	5.3.2

Note:

There is no specific description of Implementation, Operations, and Notes for this functionality.

In the in-process HTTP server, you can control the number of request processing threads created by the in-process HTTP server by setting the number of Web clients that can connect simultaneously. Also, by pooling the constant number of request processing threads that are not running as the spare threads, the processing required for adding and deleting the request processing threads is restrained to the minimum.

Organization of this section

5.3.1 Overview of controlling the number of connections from the Web client

5.3.2 Execution environment settings (J2EE server settings)