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 36600200B64 for ; Tue, 2 Aug 2016 11:02:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3518A160A8C; Tue, 2 Aug 2016 09:02:53 +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 7D176160A76 for ; Tue, 2 Aug 2016 11:02:52 +0200 (CEST) Received: (qmail 99860 invoked by uid 500); 2 Aug 2016 09:02:51 -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 99845 invoked by uid 99); 2 Aug 2016 09:02:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Aug 2016 09:02:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EBF151A1381 for ; Tue, 2 Aug 2016 09:02:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 9u3A5TFux7m6 for ; Tue, 2 Aug 2016 09:02:49 +0000 (UTC) Received: from DUB004-OMC4S14.hotmail.com (dub004-omc4s14.hotmail.com [157.55.2.89]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 859CF6124F for ; Tue, 2 Aug 2016 09:02:48 +0000 (UTC) Received: from DUB112-W24 ([157.55.2.72]) by DUB004-OMC4S14.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 2 Aug 2016 02:02:40 -0700 X-TMN: [bDQOH3HsMZgBZ+jtb+9w/8DfFVozVM61GOjsat6lA8M=] X-Originating-Email: [adelboutros@live.com] Message-ID: Content-Type: multipart/alternative; boundary="_34b54954-ee61-434c-bdea-74e425976eb4_" From: Adel Boutros To: "users@qpid.apache.org" Subject: RE: [Qpid dispatch router] Do we need a broker to send/receive messages? Date: Tue, 2 Aug 2016 11:02:40 +0200 Importance: Normal In-Reply-To: References: ,<3e95d1be-e033-421e-e77c-920ab5045c09@redhat.com>, MIME-Version: 1.0 X-OriginalArrivalTime: 02 Aug 2016 09:02:40.0686 (UTC) FILETIME=[9F9524E0:01D1EC9C] archived-at: Tue, 02 Aug 2016 09:02:53 -0000 --_34b54954-ee61-434c-bdea-74e425976eb4_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello again=2C If the address is configured with "balanced"=2C I am unable to exchange mes= sages. When using "multicast" it worked. Is this expected? Regards=2C Adel > From: adelboutros@live.com > To: users@qpid.apache.org > Subject: RE: [Qpid dispatch router] Do we need a broker to send/receive m= essages? > Date: Thu=2C 28 Jul 2016 16:51:50 +0200 >=20 > Thank you Ted and Paolo=2C > Actually I tried to have only a publisher connected and it was hanging. N= ow I understand why: It is because I need a consumer connected to get credi= ts. > Regards=2CAdel >=20 > > Subject: Re: [Qpid dispatch router] Do we need a broker to send/receive= messages? > > To: users@qpid.apache.org > > From: tross@redhat.com > > Date: Thu=2C 28 Jul 2016 10:47:43 -0400 > >=20 > >=20 > > On 07/28/2016 10:17 AM=2C Adel Boutros wrote: > > > Hello=2C > > > > > > Out of curiosity=2C Can I send/receive messages with a queue defined = directly on the dispatch router or do I need to have a real instance of a b= roker connected to that dispatcher? > >=20 > > Like Paolo said=2C you only need a broker if you want to store the mess= age=20 > > in a queue. > >=20 > > You can use the router(s) to communicate directly by having the senders= =20 > > and receivers use the same address. In this case=2C the exchange of=20 > > messages (acknowledgement=2C settlement=2C etc.) are routed directly be= tween=20 > > the senders and the receivers. > >=20 > > To do this=2C you don't need a route-container connection and you don't= =20 > > need auto-links or link-routes. You only need to configure the address= =20 > > prefix to control whether the deliveries are multicast (all receivers=20 > > for the address) or anycast (one receiver for the address). Addresses= =20 > > that don't match any configured prefix default to balanced-anycast. > >=20 > > You can use a hybrid approach as well=2C with some addresses defined as= =20 > > "waypoint" with autolinks and other addresses that are not "waypoint"=20 > > that are used for direct producer-to-consumer communication. > >=20 > > > > > > I am asking because it seems that the dispatch router has by default = some "Addresses" used for internal communication and I was wondering if I c= ould create an "address" of a type queue and use it directly without adding= connectors. > > > > > > Router Addresses > > > class addr phs distrib in-proc local remote= cntnr in out thru to-proc from-proc > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > local $_management_internal closest 1 0 0 = 0 0 0 0 0 0 > > > local $displayname closest 1 0 0 = 0 0 0 0 0 0 > > > mobile $management 0 closest 1 0 0 = 0 3 0 0 3 0 > > > local $management closest 1 0 0 = 0 0 0 0 0 0 > > > local temp.9yqNIIHanFkSZbe closest 0 1 0 = 0 0 0 0 0 0 > > > > > > > > > Regards=2C > > > Adel > > > =09 > > > > >=20 > > --------------------------------------------------------------------- > > To unsubscribe=2C e-mail: users-unsubscribe@qpid.apache.org > > For additional commands=2C e-mail: users-help@qpid.apache.org > >=20 > =20 = --_34b54954-ee61-434c-bdea-74e425976eb4_--