In the in-process HTTP server, you control the number of concurrent connections from the Web client by specifying the maximum number of connections from the Web client along with the number of requests for which connection is rejected.

When the number of connections from the Web client increases or if the load on the J2EE server increases with the effect of the J2EE applications, the Web client can instantly receive a response by rejecting the receipt of requests from the Web client and by returning an error immediately. As a result, the load on the J2EE server is controlled constantly and the response time for the request can be maintained.

The value obtained by subtracting the number of requests for which the connection is rejected from the maximum number of connections by the Web client is the number of requests for which connection is approved by the Web client.

The following figure shows an overview of controlling the number of concurrent connections from the Web client:

Figure 5-5 Overview of controlling the number of concurrent connections from the Web client

For example, assuming the maximum number of connections from the Web client is 40 and the number of requests for which connection is rejected is 1, the number of Web clients that can concurrently process the requests by connecting to the in-process HTTP server is 39. If the number of threads that are processing the requests becomes 39, the remaining 1 thread continues to return an error for the received requests until the number of request processing threads (under processing) will reduce. The following figure shows an example of controlling the number of concurrent connections from the Web client:

Figure 5-6 Example of controlling the number of concurrent connections from the Web client

By controlling the number of concurrent connections from the Web client, an error with the status code 503 is returned to the Web client for the request for which connection is rejected. At this time, if you customize the error page returned to the client, you can customize the response message or redirect to another server.

For details on the settings for customizing the responses to the Web client (in the in-process HTTP server), see 5.14 Customizing responses to the Web client using HTTP responses and 5.15 Error page customization (In-process HTTP server).

Note

When displaying a page with a frame or a page with an inserted image, the multiple requests might be received from the Web client. In this case, the pages displayed by controlling the number of concurrent connections from the Web client might result in partial errors.