Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com AFA84C05B1E9
Date: Thu, 30 Mar 2017 10:10:05 -0400 (EDT)
From: Ganesh Murthy <gmurthy@redhat.com>
To: users@qpid.apache.org
Cc: Alan Conway <aconway@redhat.com>
Message-ID: <1087971925.7566343.1490883005989.JavaMail.zimbra@redhat.com>
In-Reply-To: <CAHh5=gsR17r1BAOOqdhKCidY-uxtAtwW0nOFAccVH5tLRH4WdA@mail.gmail.com>
References: <CA+g_sc0H9uv7hx4+EGCuc+58OOQgR1d_GjiqLQHeihFbT-cuZw@mail.gmail.com> <1488983621.2612.16.camel@redhat.com> <375b4b9a-0084-b75a-dbf5-6c75cfd8f95e@redhat.com> <CACsaS96DT+Lfv0SOFpXoT+vvsgOGxYFHRKWc0prDFQd=k51z0Q@mail.gmail.com> <CAHh5=gsR17r1BAOOqdhKCidY-uxtAtwW0nOFAccVH5tLRH4WdA@mail.gmail.com>
Subject: Re: Configuring addresses starting with '/' on qpid-dispatch router
 0.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: Configuring addresses starting with '/' on qpid-dispatch router 0.7.0
Thread-Index: 5exh3vV1SsTSvfXA6wj6A/UbsZgDiw==
archived-at: Thu, 30 Mar 2017 14:10:17 -0000


----- Original Message -----
> From: "Olivier Mallassi" <olivier.mallassi@gmail.com>
> To: users@qpid.apache.org
> Cc: "Alan Conway" <aconway@redhat.com>
> Sent: Wednesday, March 29, 2017 3:30:48 PM
> Subject: Re: Configuring addresses starting with '/' on qpid-dispatch rou=
ter 0.7.0
>=20
> To complement and certainly explain the need, We would like urls like
> amqp://ip:port/domain/subdomain1/queueA or
> amqp://ip:port/domain/subdomain2/queueB
>  + use routing capabilities to route queueA, queueB on different brokers =
or
> even queueA to brokers and queueB to another dispatch-router (e.g. for
> external integration)
>=20
> I did some really quick and basic tests using the dispatch-router.
> =C2=A7 qdmanage create --type org.apache.qpid.dispatch.router.config.auto=
Link
> addr=3D/domain/subdomain/queueA dir=3Din connection=3Dbroker3
> =C2=A7 sending / receiving messaging using the simple_recv/send.py script=
s.
>=20
> It appears that the messages are well published / consumed. sounds correc=
t
> to you?
>=20
> yet (and this is not really important), the qdstat displays weird labels
>=20
> mobile      queue.first            0               0      0       0    0
> 0     0        0
>=20
>   local       temp.2ndwYNc5ZaHaD2O                   1      0       0
> 0    0     0        0
>=20
>   unknown: s  ubdomain/queueA                        1      0       200
> 200  0     0        0
>=20
>   unknown: s  ubdomain/queueA                        0      0       0
> 0    0     0        0
>=20
> version used: dispatch-router 0.7.0
>=20
The above qdstat output does look weird. Can you please enter a JIRA detail=
ing the steps we can use to reproduce this this problem?=20
Thanks.
>=20
> On Wed, Mar 29, 2017 at 12:15 PM, Rob Godfrey <rob.j.godfrey@gmail.com>
> wrote:
>=20
> > On 29 March 2017 at 11:48, Ted Ross <tross@redhat.com> wrote:
> >
> > >
> > >
> > > On 03/08/2017 02:33 PM, Alan Conway wrote:
> > >
> > >> On Fri, 2017-03-03 at 09:58 +0000, Antoine Chevin wrote:
> > >>
> > >>> Hello,
> > >>>
> > >>> Do you have an idea on the below behavior?
> > >>>
> > >>
> > >> This is related to early drafts of the AMQP addressing specification=
,
> > >> but those are out of date now and the specification is still not
> > >> released.
> > >>
> > >> Given that, I think this behavior is probably not helpful - dispatch
> > >> should accept address exactly as provided by the user and do no
> > >> modification. I'm not 100% sure if that would cause any internal
> > >> problems for the router, if not we should raise an issue.
> > >>
> > >> Ted do you have any thoughts?
> > >>
> > >
> > > Dispatch normalizes addresses to make sure that various "equivalent"
> > forms
> > > are hashed to the same entry in the address table.
> > >
> > > As Alan pointed out, we use a URL-like address format per early draft=
s of
> > > the addressing specification.  As such, the leading slash is removed =
from
> > > the normalized address.
> > >
> > >
> > What are the normalization rules, and why is dispatch assuming that
> > removing a leading slash is correct (since in this case it is not - the
> > Java Broker does its own normalization - and if you want you can query =
it
> > and find out what prefixes it considers equivalent)?
> >
> > -- Rob
> >
> >
> > >
> > >
> > >>
> > >>> Thank you,
> > >>> Regards,
> > >>> Antoine
> > >>>
> > >>> -----Original Message-----
> > >>> From: Antoine Chevin [mailto:antoine.chevin@gmail.com]
> > >>> Sent: jeudi 2 mars 2017 10:43
> > >>> To: users@qpid.apache.org
> > >>> Subject: Configuring addresses starting with '/' on qpid-dispatch
> > >>> router
> > >>> 0.7.0
> > >>>
> > >>> Hello,
> > >>>
> > >>> I tried to configure addresses starting with a '/' but using qdstat=
 I
> > >>> see
> > >>> that this '/' is removed. Is it expected?
> > >>> I noticed the same behavior with autolinks.
> > >>>
> > >>> Thank you,
> > >>> Regards,
> > >>> Antoine
> > >>>
> > >>
> > >>
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > > For additional commands, e-mail: users-help@qpid.apache.org
> > >
> > >
> >
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org