You can set a timeout period in the Web container, for sending a response to the redirector. You can detect the occurrence of failure in the redirector using the communication timeout that was set up. You can detect the following failures:

Detectable failures

• The host on which the redirector is running is down.
• A network failure occurs between the Web container and the redirector.

When the communication timeout occurs, KDJE39507-E (timeout occurred when sending a response) is output to the message log. The following table describes the conditions for occurrence of communication timeout and the operations after the timeout occurs.

Table 4-14 Conditions for occurrence of communication timeout and the operations after occurrence

Timing of occurrence of communication timeout	Operation of the method after occurrence of communication timeout	Operation of servlets or JSPs after occurrence of communication timeout
When response data is sent to the client by using the method of javax.servlet.ServletOutputStream class acquired by getOutputStream method of javax.servlet.ServletResponse class, in the servlet	Exception java.net.SocketTimeoutException occurs.	Since the connection to the redirector is closed, you cannot send or receive the request data and the response data.
When response data is sent to the client by using the method of java.io.PrintWriter class acquired by getWriter method of javax.servlet.ServletResponse class, in the servlet	The send process is interrupted and returned.	The checkError method of java.io.PrintWriter class returns true. Since the connection to the redirector is closed, you cannot send or receive the request data and the response data.
When response data is sent to the client by using the method of javax.servlet.jsp.JspWriter class, in JSP	Exception java.net.SocketTimeoutException occurs.	Since the connection to the redirector is closed, you cannot send or receive the request data and the response data.
When the response data of static contents is sent to the client	--	--

Legend:

--: Not applicable

When a request is sent to the Web container, the redirector awaits for a response from the Web container. You can set the timeout for this response waiting time. You can detect the occurrence of failure in the Web container using the communication timeout that was set up. You can detect the following failures:

Detectable failures

• The host on which the Web container is running is down.
• A network failure occurs between the Web container and the redirector.
• A Web application failure occurs in the Web container.

The following failures occur in the Web application:

Web application failures

• A response is not returned due to an infinite loop in the servlets or JSPs processing.
• The Enterprise Bean and database are invoked as an extension of servlets or JSPs, and response from them is awaited.
• Dead lock occurs in the Web application.
• The Web application does not catch up with the server processing and is running slow during the peak access.

Operation after communication timeout in the redirector

When communication timeout occurs, the redirector disconnects the connection to the Web container, and returns error with status code 500 to the client.

Hint

Operation when timeout occurs during processing of an application

Even if the redirector times out during processing in the Web container, you cannot detect that the redirector has timed out, in the Web container.

You can detect the timeout in the redirector once the processing of the Web container finishes, and a response is transferred to the redirector. In such a case, however, since the redirector has already disconnected the connection to the Web container, an error occurs when sending a response. The following figure illustrates the operation when a timeout occurs during processing of an application.

Figure 4-20 Operation when a timeout occurs during processing of an application

The figure is explained below.

1. When a timeout occurs in the redirector, a request is sent for disconnecting the connection to the Web container.
2. Redirector sends an error code to the Web server.
3. When processing of the application in the Web container finishes, a response is sent to the redirector. However, since the connection between the redirector and the Web container is already disconnected in 1., a communication error occurs.

You can set a timeout period in the Web server, for sending data to the client. You can detect the occurrence of failure in the client by using the communication timeout that was set up. You can detect the following failures:

Detectable failures

• The host on which the client is running is down.
• A network failure occurs between the client and the Web server.
• A failure occurs in client application.