Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6AB317D49 for ; Thu, 28 Jan 2016 18:07:52 +0000 (UTC) Received: (qmail 47697 invoked by uid 500); 28 Jan 2016 18:07:40 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 47623 invoked by uid 500); 28 Jan 2016 18:07:40 -0000 Mailing-List: contact issues-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 issues@ignite.apache.org Received: (qmail 47506 invoked by uid 99); 28 Jan 2016 18:07:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jan 2016 18:07:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EB4C82C1F6B for ; Thu, 28 Jan 2016 18:07:39 +0000 (UTC) Date: Thu, 28 Jan 2016 18:07:39 +0000 (UTC) From: "Alexey Stelmak (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: =?utf-8?Q?[jira]_[Updated]_(IGNITE-2496)_MESSAGING:_Add_new_remote?= =?utf-8?Q?_listener_on_=D0=B0_=D1=81lientNode_mu?= =?utf-8?Q?st_be_performed_synchronously?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-2496?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Stelmak updated IGNITE-2496: ----------------------------------- Description:=20 Current behavior: When you add a new remote listener on the client node, th= e addition takes place asynchronously, without waiting for confirmation fro= m the client node. Required behavior: When you add a new listener on the client node, we need = to wait for confirmation from the client node (as well as it works for the = server node). It is necessary to create test (or modify IgniteMessagingWithClientTest) , = which would reproduce this bug. was: Current behavior: When you add a new remote listener on the client node, th= e addition takes place asynchronously, without waiting for confirmation fro= m the client node. Required behavior: When you add a new listener on the client node, we need = to wait for confirmation from the client node (as well as it works for the = server node). It is necessary to create test (or modify GridMessagingSelfTest) , which wo= uld reproduce this bug. > MESSAGING: Add new remote listener on =D0=B0 =D1=81lientNode must be perf= ormed synchronously > -------------------------------------------------------------------------= --------- > > Key: IGNITE-2496 > URL: https://issues.apache.org/jira/browse/IGNITE-2496 > Project: Ignite > Issue Type: Bug > Components: messaging > Reporter: Alexey Stelmak > > Current behavior: When you add a new remote listener on the client node, = the addition takes place asynchronously, without waiting for confirmation f= rom the client node. > Required behavior: When you add a new listener on the client node, we nee= d to wait for confirmation from the client node (as well as it works for th= e server node). > It is necessary to create test (or modify IgniteMessagingWithClientTest) = , which would reproduce this bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)