What Internet Browser are you using? It appears that a web server and a web browser both can determine how long to wait for the other.
http://support.microsoft.com/kb/q181050/ CAUSE By design, Internet Explorer imposes a time-out limit for the server to return data. The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x and 6. As a result, Internet Explorer does not wait endlessly for the server to come back with data when the server has a problem. http://support.microsoft.com/kb/813827 This article describes how to change the default HTTP keep-alive value in Microsoft Internet Explorer. When Internet Explorer establishes a persistent HTTP connection with a Web server (by using Connection: Keep-Alive headers), Internet Explorer reuses the same TCP/IP socket that was used to receive the initial request until the socket is idle for one minute. After the connection is idle for one minute, Internet Explorer resets the connection. A new TCP/IP socket is used to receive additional requests. You may want to change the HTTP KeepAliveTimeout value in Internet Explorer. If either the client browser (Internet Explorer) or the Web server has a lower KeepAlive value, it is the limiting factor. For example, if the client has a two-minute timeout, and the Web server has a one-minute timeout, the maximum timeout is one minute. Either the client or the server can be the limiting factor. By default, Internet Explorer has a KeepAliveTimeout value of one minute and an additional limiting factor (ServerInfoTimeout) of two minutes. Either setting can cause Internet Explorer to reset the socket. David Stevenson On Fri, 2004-12-03 at 09:28, Jiang, Peiyun wrote: > I have a servlet that is doing a lot of work. After the work is done, I send > out information to say that the work is done. But somehow tomcat > disconnected and the browser is not getting the whole output. I logged the > whole process and it does run to end. If I reduce the amount of work done by > the middle process, everything is OK. I'm confuded and could not figure out > why. Please help. > > (1) Who decide to disconnect? Tomcat or the browser? I guess when the > processing is going, the browser may treat the server as NOT RESPONDING. > (2) How to keep the connection alive? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
