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 AE9262004F5 for ; Fri, 1 Sep 2017 14:27:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AD0BB16CE24; Fri, 1 Sep 2017 12:27:17 +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 265F116CE22 for ; Fri, 1 Sep 2017 14:27:16 +0200 (CEST) Received: (qmail 96645 invoked by uid 500); 1 Sep 2017 12:27:16 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 96633 invoked by uid 99); 1 Sep 2017 12:27:16 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Sep 2017 12:27:16 +0000 Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 162CA1A00C7 for ; Fri, 1 Sep 2017 12:27:14 +0000 (UTC) Received: by mail-lf0-f48.google.com with SMTP id d202so203525lfd.5 for ; Fri, 01 Sep 2017 05:27:13 -0700 (PDT) X-Gm-Message-State: AHPjjUhq5lX6BlMgPm3UzpdoboChKliMuLIjxBxEh2FoKE6MiJjvbFLB W7XAuALPRG3+LyeLfQ5cuSSukMkWFycx X-Google-Smtp-Source: ADKCNb5fADp9EkMILDtuE/A+5z72mtYkJKFsos9glEEikrklLAvws+jgXIHo38FmWj4v526Gn2xNuS3w1YVeJP6zgNU= X-Received: by 10.25.198.78 with SMTP id w75mr689340lff.211.1504268831674; Fri, 01 Sep 2017 05:27:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.83.12 with HTTP; Fri, 1 Sep 2017 05:27:10 -0700 (PDT) In-Reply-To: References: From: Yakov Zhdanov Date: Fri, 1 Sep 2017 15:27:10 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Hopeless looping in TcpCommunicationSpi To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c19d2d05c2a2805581fe144" archived-at: Fri, 01 Sep 2017 12:27:17 -0000 --94eb2c19d2d05c2a2805581fe144 Content-Type: text/plain; charset="UTF-8" Ilya, I reviewed your test and I now see the point. Is the same possible with server-server? Or failure process will be initiated for remote node by local one? Will the following work for client? If connection fails then client takes a pause for 1 sec with Thread.sleep() and takes another attempt. If maxConnectionAttempts (3 by default) fails then client stops and restart itself. --Yakov --94eb2c19d2d05c2a2805581fe144--