From tomcat-user-return-119552-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Mon Jan 17 16:15:42 2005 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 68840 invoked from network); 17 Jan 2005 16:15:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Jan 2005 16:15:42 -0000 Received: (qmail 72960 invoked by uid 500); 17 Jan 2005 16:15:01 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 72917 invoked by uid 500); 17 Jan 2005 16:15:01 -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 72896 invoked by uid 99); 17 Jan 2005 16:15:00 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.zooplus.de (HELO mail.zooplus.de) (212.18.25.230) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 17 Jan 2005 08:14:59 -0800 Received: from exchange2.home.zooplus.de (unknown [192.168.10.72]) by mail.zooplus.de (Postfix) with ESMTP id 16A145762E for ; Mon, 17 Jan 2005 17:14:56 +0100 (CET) Received: by exchange2.home.zooplus.de with Internet Mail Service (5.5.2657.72) id ; Mon, 17 Jan 2005 17:06:56 +0100 Message-ID: <10361639FF4CA04ABB30F54683E4FB85878F40@exchange2.home.zooplus.de> From: Bernhard Slominski To: 'Tomcat Users List' Subject: AW: Long running requests and timeouts? Date: Mon, 17 Jan 2005 17:06:55 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Andrzej, one possible workaround is compress the output, so the response is compressed with zip compresseion and your response gets shorter. You need a response filter for that, if this is an option an you need = more details let me know. Cheers Bernhard -----Urspr=FCngliche Nachricht----- Von: Andrzej Jan Taramina [mailto:andrzej@chaeron.com] Gesendet: Montag, 17. Januar 2005 16:25 An: tomcat-user@jakarta.apache.org Betreff: Long running requests and timeouts? I have a situation where some requests that get sent to Tomcat are very = long running (basically batch operations). I've been testing with a request = that takes just over 7 minutes to process and returns and XML document as a=20 response. The problem I'm having is that the response gets truncated. It's = always=20 truncated at a consistent spot (3207 characters for some reason, that's = what Firefox reports). Shorter running requests don't truncate anything, regardless of how = long the response might be. I'm running Tomcat 5.0.28 and my Connector in the Tomcat server.xml = file=20 looks like: Is the connectionTimeout value the one that might be contributing to = this=20 behaviour? Are there any other timeout settings that might affect this? Thanks! Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.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