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 43AD3200CBD for ; Thu, 6 Jul 2017 19:12:30 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 42577166F26; Thu, 6 Jul 2017 17:12:30 +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 87586166F22 for ; Thu, 6 Jul 2017 19:12:29 +0200 (CEST) Received: (qmail 14328 invoked by uid 500); 6 Jul 2017 17:12:28 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 14316 invoked by uid 99); 6 Jul 2017 17:12:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jul 2017 17:12:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EDBE8191739 for ; Thu, 6 Jul 2017 17:12:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.029 X-Spam-Level: *** X-Spam-Status: No, score=3.029 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_ADVERT2=0.55, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id uurTW9efk5k6 for ; Thu, 6 Jul 2017 17:12:25 +0000 (UTC) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 1BD445FC3D for ; Thu, 6 Jul 2017 17:12:25 +0000 (UTC) Received: by mail-it0-f46.google.com with SMTP id k192so9979438ith.1 for ; Thu, 06 Jul 2017 10:12:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sk+ER3S++sc32k7fO9KnIfjT+PTh6iOld9F2XNN6GD8=; b=GrJPBfktyZvFF8K7SroVDS+8ztdtfSMsa4/JbVR/UkwyHOd3YFIEeC2opN1iabCJ3L /WepS5rD6vqQdJe9yP1XtVJCHDlrxZl79b4N6y0SKQXzZabjVi6vlIQk7MqSeAUPmlJW lTH9UGlvXyCWuX9b83DFwp6VODt5on4lx/ernLdUmX9PJt20e9GTZjvrEmiq7VjgfhzG DusUN2Ru7OSB11jQ9wX9CbNiTxGOJ8jwwPmwZoHE43xfGniOz+PnSMEBSWV2HgEwyZ2o +4vNbrcHLHii/d3ZaTo0ywn6xnPYw3QRbCG24Gy1RsEnEvE/ev4iGmgCKdVMPw11CEds QoaA== X-Gm-Message-State: AIVw112fHH1/Av0dxRBb/20Wy3cmpvNB3uaaPpkuDjQlcMXV1m1kXYIU YScYMnJQXD3u2qlCXkHhBmVB4RefyfsE X-Received: by 10.36.36.131 with SMTP id f125mr205380ita.37.1499361143635; Thu, 06 Jul 2017 10:12:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.38.196 with HTTP; Thu, 6 Jul 2017 10:12:23 -0700 (PDT) In-Reply-To: References: <9d8b2938-97bf-7efe-1338-f720677a6d3b@redhat.com> From: Ted Ross Date: Thu, 6 Jul 2017 13:12:23 -0400 Message-ID: Subject: Re: [Dispatch Router] List of connected producers To: users@qpid.apache.org Content-Type: multipart/alternative; boundary="001a1147c69c5b562e0553a938de" archived-at: Thu, 06 Jul 2017 17:12:30 -0000 --001a1147c69c5b562e0553a938de Content-Type: text/plain; charset="UTF-8" On Wed, Jul 5, 2017 at 5:05 PM, Adel Boutros wrote: > Thank you both, > > > I will try what you suggested. > > > I was wondering why the phases are actually named "0" and "1" as this a > bit confusing. Wouldn't a more meaningful string representation be better > especially for the users? > > The most common case is the single-waypoint case, where the configuration doesn't involve phases (they're hidden behind the "waypoint" attribute). You can have up to ten phases (0..9) for an address if there are multiple waypoints involved for a message flow, but this is an advanced and uncommon setup. The idea behind the phase number is that the address phase sequences through the values as the message moves from producer to waypoint [to waypoint]* to consumer. > > Adel > > ________________________________ > From: Gordon Sim > Sent: Wednesday, July 5, 2017 9:25:06 PM > To: users@qpid.apache.org > Subject: Re: [Dispatch Router] List of connected producers > > On 05/07/17 20:01, Ted Ross wrote: > > You can query a list of links (org.apache.qpid.dispatch.router.link) > with > > attribute "owningAddr" equal to the addresses of the waypoint (phase 0 > for > > producers, phase 1 for consumers). I believe that the auto-links will > also > > be included in this list, but can be identified by the reversal of the > > direction (i.e. phase 0 out-links and phase 1 in-links are not clients). > > You can also filter out the autolinks by selecting only those > linkType==endpoint I believe. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > > --001a1147c69c5b562e0553a938de--