Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7FD2BF85B for ; Thu, 21 Mar 2013 14:11:37 +0000 (UTC) Received: (qmail 32301 invoked by uid 500); 21 Mar 2013 14:11:37 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 32212 invoked by uid 500); 21 Mar 2013 14:11:36 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 32198 invoked by uid 99); 21 Mar 2013 14:11:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 14:11:36 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of asankha.apache@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-da0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Mar 2013 14:11:30 +0000 Received: by mail-da0-f43.google.com with SMTP id u36so1668325dak.2 for ; Thu, 21 Mar 2013 07:11:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=GZZVHqOdtbufSm75whnAEXx8QnnB6En99mzM5f+4po8=; b=C3ko7Cb2uwndS48IQBQUbiXiJx4wPQtiayDFmPYPqYmWFGxIqBahHpIrmww36cHmQ0 /SvDMuQB9+RdwaxOAj4Z/amRaBmBaZsPF9OhxGJxkUqY0REV4C3fEvKw4k61gR2uBRAE 0KKNMFVD4T26ZIAzAwnhoq0Tan2Urdb4IlBSASV49s2L2pUbf3eBoykmYjiq8Z2LmzNd O4gUezV4pXmq//sFfv10+Q52haZ1ztq8tLpB6lpqQFYh+hv6Gp0yy1flDoHDg1ZnDWEV 9OBFZlrVI4wi+Sx12LS0tew81+Df/1DU0SsV5Oj1vayOTl6jCiokO3OdePQeL20Y++n7 SIRg== X-Received: by 10.68.11.135 with SMTP id q7mr14978425pbb.5.1363875068900; Thu, 21 Mar 2013 07:11:08 -0700 (PDT) Received: from [192.168.1.100] ([112.134.145.78]) by mx.google.com with ESMTPS id dl1sm6251652pbc.17.2013.03.21.07.11.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Mar 2013 07:11:07 -0700 (PDT) Sender: Asankha Perera Message-ID: <514B14F7.6040408@apache.org> Date: Thu, 21 Mar 2013 19:41:03 +0530 From: "Asankha C. Perera" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: dev@hc.apache.org Subject: Questions about Connection Pooling with 4.2.x Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi All Should we internally update the socket timeout on the pooled connection when one calls PoolEntry.updateExpiry()? Also, I am trying to fix a corner case bug, where we submit a request through the HttpAsyncRequester.execute(). There is a connection in the pool, which is later found to have timed out - shouldn't the system automatically get a new connection and attempt the send? regards asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org