Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 11309 invoked from network); 12 Nov 2003 13:39:02 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Nov 2003 13:39:02 -0000 Received: (qmail 1977 invoked by uid 500); 12 Nov 2003 13:38:40 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 1686 invoked by uid 500); 12 Nov 2003 13:38:38 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 1673 invoked from network); 12 Nov 2003 13:38:38 -0000 Received: from unknown (HELO sid.armstrong.com) (204.74.20.252) by daedalus.apache.org with SMTP; 12 Nov 2003 13:38:38 -0000 Received: from joedog.org (fnord.armstrong.com [204.74.20.14]) by sid.armstrong.com (8.12.8p1/8.12.8) with ESMTP id hACDS2C0027086 for ; Wed, 12 Nov 2003 08:28:03 -0500 Message-ID: <3FB237DF.3080504@joedog.org> Date: Wed, 12 Nov 2003 08:38:39 -0500 From: Tim Funk Organization: Human being User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en, es-mx, de, sv MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat Settings advice on long-running process. References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N During the middle of processing, the browser drops the socket. This casues the next write by tomcat to fail with a Socket exception (Actually ClientAbort or similar). One workaround is to put the long running operation in its own thread (carefully) and have the thread update a "status" object which lives in a session. (Or static singleton if your feeling lucky/brave). Then the browser displays the contents of the "status" object and has a META refresh every {insert here} seconds. If the long running process did its thing, your can then display the alternate results/download file/whatever. -Tim Elankath, Tarun (Cognizant) wrote: > Hi list, > > We have a long running process (all in java, not external) that is initiated from struts action class, (does a lot of file I/O, etc) > > The browser apparently timesout after about 20 minutes or whereabouts, and then suddenly the process do stops bang in the middle as soon as this happens. This is quite puzzling as one expects the process to continue even if the browser timed out. > > I do know the correct solution is to make it run in the background and give constant updates to the user, however, we just need to make it work ASAP with the correct approach. We'll migrate to the background process & progress page approach soon enough. > > Any pointers/comments on browser (Internet Explorer), server (Tomcat) settings and Struts settings to handle long-running activities in the web-request cycle would be greatly appreciated. I did scout the web, but apart from the connectionTimeout setting in the element of tomcat, I didn't find anything much. I don't think increasing session-timeout would be of any help here. > > Any pointers on how to avoid the 'freeze' would also be much appreciated. > > Thank you, > Tarun > > > ------------------------------------------------------------------------ > > > This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. > If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. > Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly > prohibited and may be unlawful. > > Visit us at http://www.cognizant.com > > > > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org