Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A8FF6200BB8 for ; Sat, 12 Nov 2016 16:26:27 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A7956160B00; Sat, 12 Nov 2016 15:26:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EC54E160AF4 for ; Sat, 12 Nov 2016 16:26:26 +0100 (CET) Received: (qmail 5491 invoked by uid 500); 12 Nov 2016 15:26:26 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 5480 invoked by uid 99); 12 Nov 2016 15:26:26 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Nov 2016 15:26:26 +0000 Received: from ok2c (unknown [185.25.95.132]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 2C29F1A0185 for ; Sat, 12 Nov 2016 15:26:24 +0000 (UTC) Message-ID: <1478964381.24148.10.camel@apache.org> Subject: Re: SSL Handshake : timing and timeout From: Oleg Kalnichevski To: HttpClient User Discussion Date: Sat, 12 Nov 2016 16:26:21 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.9-1+b1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit archived-at: Sat, 12 Nov 2016 15:26:27 -0000 On Fri, 2016-11-11 at 11:01 +0100, Stefan Magnus Landrø wrote: > True. The way SSL sockets are created is complex stuff. They are layered > and I believe the handshake is async - maybe Oleg could clarify? > There is nothing special or unusual about SSL/TLS handshakes. They involve multiple IP packet exchanges over a TCP connection. Standard socket settings fully apply. Oleg > Anyways - We ran into an issue a few years ago with an SSL handshake taking > for ever (a switch was dropping packets of a certain size ... ), and > tracked our hanging threads down to blocking because the SoTimeout was set > to 0 by default. Changing this prevented threads from hanging for ever. > > Ref javadoc: > > Determines the default socket timeout value for non-blocking I/O operations. > > 2016-11-11 10:01 GMT+01:00 Philippe Mouawad : > > > Thanks but I see not property related to Ssl Handshake timeout. > > > > Regards > > > > On Friday, November 11, 2016, Stefan Magnus Landrø < > > stefan.landro@gmail.com> > > wrote: > > > > > https://hc.apache.org/httpcomponents-client-ga/ > > > httpclient/apidocs/org/apache/http/impl/client/HttpClientBuilder.html# > > > setDefaultSocketConfig(org.apache.http.config.SocketConfig) > > > > > > 2016-11-11 9:34 GMT+01:00 Philippe Mouawad > > >: > > > > > > > Thank you Stefan > > > > Could you point me to some doc ? > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org