Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA5CB64C0 for ; Wed, 22 Jun 2011 13:44:05 +0000 (UTC) Received: (qmail 19111 invoked by uid 500); 22 Jun 2011 13:44:01 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 19017 invoked by uid 500); 22 Jun 2011 13:44:01 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 19008 invoked by uid 99); 22 Jun 2011 13:44:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2011 13:44:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2011 13:43:55 +0000 Received: from [192.168.245.129] (montserrat.wissensbank.com [212.85.37.175]) by tor.combios.es (Postfix) with ESMTPA id 3B78E22611C for ; Wed, 22 Jun 2011 15:43:29 +0200 (CEST) Message-ID: <4E01F166.104@ice-sa.com> Date: Wed, 22 Jun 2011 15:43:02 +0200 From: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Apache Tomcat 7.0.14 References: <4E01C878.8090409@ice-sa.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I don't think that az this stage you should be playing with the socket.* attributes, which refer to the low-level JVM TCP socket, and have quite another meaning and other side-effects. Re-read the description of the "keepAliveTimeout" attribute instead, which does refer to the HTTP protocol level. As a general rule : the default values for the Connector attributes have generally been chosen to be reasonable and fit the most usual use cases. Only modify them if you have a specific and precise reason to do so, after doing adequate measurements. adarsh thimmappa wrote: > Hi Andre, > I am using the below Connector tag configuration in the > server.xml.....I am still facing the same problem. > > protocol="org.apache.coyote.http11.Http11NioProtocol" > socket.soKeepAlive="true" > socket.soTimeout="3600000" > maxKeepAliveRequests="-1" > redirectPort="8443" /> > > > > > > Thanks, > Adarsh > > > > > On Wed, Jun 22, 2011 at 4:18 PM, André Warnier wrote: > >> adarsh thimmappa wrote: >> >>> Hi All, >>> I am using Apache Tomcat 7.0 (7.0.14 version) server. I have a >>> requirement such that Once i make a HTTP request, and get back the >>> response, >>> i want to keep that connection alive indefinitely. What is the >>> configuration >>> i need to make on the server side. By default, client uses HTTP/1.1 >>> protocol >>> version to make HTTP requests. I know that in HTTP/1.1, the Connection is >>> kept alive by default. I am testing this setup on localhost. >>> >>> >>> * Any help or suggestions will be appreciated.* >>> >>> Maybe reading the on-line documentation ? >> http://tomcat.apache.org/**tomcat-7.0-doc/config/http.** >> html#Common_Attributes >> >> keepAliveTimeout >> maxKeepAliveRequests >> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org