8.6.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 8-9 or Figure 8-10.
- Tip
-
When sending requests directly to and from the J2EE server without going through the Web server, you can set timeouts at points 5 to 13. Points 1 to 4 do not apply in this situation.
|
|
![[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 timeout is used to release Web server resources. When there is a backlog of responses to the Web browser (when the Web browser is not receiving the responses), the timeout is used to release resources for the Web server and for the Web container in the J2EE server.
The waiting time is set to the same value in each case. A timeout can only be set at point 1 in the case of Web server integration.
-
Waiting time for sending requests to the Web container in the reverse proxy registered in the Web server (points 2 and 3)
When sending a request from the reverse proxy to the Web container, control might be lost if a problem occurs in the Web container itself or in the communication path between the Web server and the Web container. In this case, the timeout triggers the release of Web server resources. 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 in the reverse proxy registered in the Web server (point 4)
If control is lost due to a problem in the J2EE application, the timeout triggers the release of Web server resources. 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
-
Timeout points are set at the level of the reverse proxy data transfer destination. For this reason, if the time required for processing varies from business process to business process, we recommend that you define reverse proxy data transfer destinations at the level of Web applications corresponding to business processes and set timeouts accordingly.
-
Waiting time for receiving data from the reverse proxy or the Web client in the Web container (point 5)
In the case of Web server integration, when sending a request from the reverse proxy to the Web container, a backlog of requests might form due to a problem in the Web server itself or a problem in the communication path between the Web server and the Web container. In this case, the timeout triggers the release of J2EE server (Web container) resources.
When sending and receiving requests directly to and from the J2EE server without going through the Web server, when there is a backlog of requests from the Web browser, the timeout triggers the release of J2EE server (Web container) resources.
-
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. See 8.6.7 Setting the method timeout in the J2EE application.
-
Waiting time for sending response from the Web container to the reverse proxy or the Web client (point 13)
In the case of Web server integration, when sending a response from the Web container to the reverse proxy, control might be lost due to a problem in the Web server itself or a problem in the communication path between the Web server and the Web container. In this case, the timeout triggers the release of Web container resources.
When sending and receiving requests directly to and from the J2EE server without going through the Web server, if communication with the Web browser is stalled, the timeout triggers the release of Web container resources.