17.4.2 Setting the timeout in a Web front-end system
This section explains the settings of timeout in a Web front-end system.
When setting the timeout in a Web front-end system, amongst all the timeout values for the entire system, you need to consider points 1 to 6 and 13 shown in the following figure. These numbers correspond to Figure 17-2 or Figure 17-3.
- Tip
-
When you use an in-process HTTP server, you can set up points 1 and 6. The points 2 to 5, and 13 are not applicable.
|
|
![[Figure]](GRAPHICS/ZU061100.GIF)
-
Waiting time in the Web server for receiving requests from the client and sending the data to the client (point 1)
When there is a backlog of requests from the Web browser, the redirector resources will be released according to the timeout. When there is a backlog of responses to the Web browser, (when the Web browser does not receive the responses), the resources of the Web container in the redirector and the J2EE server will be released according to the timeout.
In the case of a Web server integration, the same values are set in the above waiting time settings.
When you use an in-process HTTP server, you can specify different values for the waiting time for receiving requests from the client, and the waiting time for sending data to the client.
-
Waiting time for sending requests to the Web container of the redirector that is registered in the Web server (points 2 and 3)
When the redirector sends a request to the Web container and the control does not return due to an error in the Web container or an error in the communication path between the redirector and the Web container, the redirector resources will be released according to the timeout. At the same time, the error is notified to the Web browser. You can set the timeout at this point only in the case of Web server integration.
Point 2 is the waiting time for establishing connection with the Web container and Point 3 is the waiting time for the process of sending requests to the Web container.
-
Waiting time for receiving data from the Web container of the redirector registered in the Web server (point 4)
If there is an error in the J2EE application and the control does not return, the redirector resources will be released according to the timeout. At the same time, the error is notified to the Web browser. You can set the timeout at this point only in the case of Web server integration.
- Tip
-
The unit for the settings is worker. Hitachi, therefore, recommends that when the processing time differs according to the business, define the worker for each Web application corresponding to the business and set the timeout value.
-
Waiting time for receiving data from the redirector, in the Web container (point 5)
When there is a backlog of requests from the browser, the J2EE server (Web container) resources will be released. You can set the timeout at this point only in the case of Web server integration.
-
Waiting time for processing request in the Web container (point 6)
The functionality of monitoring the execution time of J2EE application is used to set this timeout. For details, see 8.6.7 Setting the method timeout in the J2EE application in the manual uCosminexus Application Server System Design Guide.
-
Waiting time for sending a response from the Web container to the redirector (point 13)
When the Web container sends a response to the redirector and the control does not return due to an error in the redirector or an error in the communication path between the redirector and the Web container, the Web container resources will be released according to the timeout. At the same time, the error is notified to the Web browser. You can set the timeout at this point only in the case of Web server integration.