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 E1334D7B2 for ; Thu, 21 Jun 2012 14:24:43 +0000 (UTC) Received: (qmail 1215 invoked by uid 500); 21 Jun 2012 14:24:43 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 1126 invoked by uid 500); 21 Jun 2012 14:24:43 -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 1032 invoked by uid 99); 21 Jun 2012 14:24:42 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jun 2012 14:24:42 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 707DD1402B5 for ; Thu, 21 Jun 2012 14:24:42 +0000 (UTC) Date: Thu, 21 Jun 2012 14:24:42 +0000 (UTC) From: "restonica (JIRA)" To: dev@hc.apache.org Message-ID: <1085998607.38919.1340288682462.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HTTPCLIENT-1208) PoolingClientConnectionManager give a new route even if keep-alive MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 restonica created HTTPCLIENT-1208: ------------------------------------- Summary: PoolingClientConnectionManager give a new route even if keep-alive Key: HTTPCLIENT-1208 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1208 Project: HttpComponents HttpClient Issue Type: Bug Components: HttpClient Affects Versions: 4.2 Final Reporter: restonica A connection is kept with a route and a specific state, for example : Connection [id: 0][route: {s}->https://x.x.x.x:8443][state: CN=KeyPair, OU=OU, O=O, L=Marseille, C=FR] can be kept alive for 30000 MILLISECONDS If a new connection with the same route is asked, for example: Connection request: [route: {s}->https://x.x.x.x:8443][total kept alive: 1; route allocated: 1 of 50; total allocated: 1 of 200] then the connection manager will give a NEW route (with a new ID). If the first kept connection (see the beginning) does not contain the state, all is OK and the connection manager give the same route as the previous one. This bug cause problem in case of SSL mutual authentication, a new TCP connection is done for each request !! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org For additional commands, e-mail: dev-help@hc.apache.org