You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Adel Boutros <ad...@live.com> on 2016/06/30 08:55:38 UTC
[Qpid Java Broker] Cannot bind fanout exchange to a queue without
specify a binding key
Hello,
In the definition of the fanout exchange[1], it is mentioned "The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key". However, using the web management console, when I create a fanout exchange, it forces me to set a binding key.
I believe this is a bug. Do you agree or did I misunderstand something?
Regards,
Adel
[1] https://qpid.apache.org/releases/qpid-java-6.0.3/java-broker/book/Java-Broker-Concepts-Exchanges.html
Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue without
specify a binding key
Posted by Rob Godfrey <ro...@gmail.com>.
Just to be clear, AMQP 0-10 *requires* that a binding key is used to
uniquely identify every binding between an exchange and a queue. It does
allow for the fact that the binding may be the empty string, however only
one binding per queue may use this binding key on the given exchange. So I
don't think it is correct to say that it is an error to *require* a binding
key, however it is overly restrictive to not allow a binding where the
binding key is the empty string.
-- Rob
On 1 July 2016 at 16:55, Adel Boutros <ad...@live.com> wrote:
> Thank you Keith,
>
> Issue raised: https://issues.apache.org/jira/browse/QPID-7339
>
> Adel
>
> > From: keith.wall@gmail.com
> > Date: Fri, 1 Jul 2016 16:43:42 +0100
> > Subject: Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue
> without specify a binding key
> > To: users@qpid.apache.org
> >
> > Hi Adel
> >
> > Yes, this is a defect in the Web Management Console (the UI). The UI
> > should not be demanding a binding key in this case. For the fanout
> > exchange, the binding is simply one between exchange and queue.
> > Actually, underneath the binding key field is used to name the Binding
> > entity that links the Queue and Exchange. It is not actually used to
> > determine routing at all for this exchange type. You can enter
> > whatever you like, providing it is unique to the scope of the queue
> > and exchange.
> >
> > Please raise a JIRA. Bindings are scheduled to get some work soon
> > (probably 6.2).
> >
> > Kind regards, Keith.
> >
> >
> > On 30 June 2016 at 09:55, Adel Boutros <ad...@live.com> wrote:
> > > Hello,
> > >
> > > In the definition of the fanout exchange[1], it is mentioned "The
> fanout exchange type routes messages to all queues bound to the exchange,
> regardless of the message's routing key". However, using the web management
> console, when I create a fanout exchange, it forces me to set a binding key.
> > >
> > > I believe this is a bug. Do you agree or did I misunderstand something?
> > >
> > > Regards,
> > > Adel
> > >
> > > [1]
> https://qpid.apache.org/releases/qpid-java-6.0.3/java-broker/book/Java-Broker-Concepts-Exchanges.html
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
>
>
RE: [Qpid Java Broker] Cannot bind fanout exchange to a queue
without specify a binding key
Posted by Adel Boutros <ad...@live.com>.
Thank you Keith,
Issue raised: https://issues.apache.org/jira/browse/QPID-7339
Adel
> From: keith.wall@gmail.com
> Date: Fri, 1 Jul 2016 16:43:42 +0100
> Subject: Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue without specify a binding key
> To: users@qpid.apache.org
>
> Hi Adel
>
> Yes, this is a defect in the Web Management Console (the UI). The UI
> should not be demanding a binding key in this case. For the fanout
> exchange, the binding is simply one between exchange and queue.
> Actually, underneath the binding key field is used to name the Binding
> entity that links the Queue and Exchange. It is not actually used to
> determine routing at all for this exchange type. You can enter
> whatever you like, providing it is unique to the scope of the queue
> and exchange.
>
> Please raise a JIRA. Bindings are scheduled to get some work soon
> (probably 6.2).
>
> Kind regards, Keith.
>
>
> On 30 June 2016 at 09:55, Adel Boutros <ad...@live.com> wrote:
> > Hello,
> >
> > In the definition of the fanout exchange[1], it is mentioned "The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key". However, using the web management console, when I create a fanout exchange, it forces me to set a binding key.
> >
> > I believe this is a bug. Do you agree or did I misunderstand something?
> >
> > Regards,
> > Adel
> >
> > [1] https://qpid.apache.org/releases/qpid-java-6.0.3/java-broker/book/Java-Broker-Concepts-Exchanges.html
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
Re: [Qpid Java Broker] Cannot bind fanout exchange to a queue without
specify a binding key
Posted by Keith W <ke...@gmail.com>.
Hi Adel
Yes, this is a defect in the Web Management Console (the UI). The UI
should not be demanding a binding key in this case. For the fanout
exchange, the binding is simply one between exchange and queue.
Actually, underneath the binding key field is used to name the Binding
entity that links the Queue and Exchange. It is not actually used to
determine routing at all for this exchange type. You can enter
whatever you like, providing it is unique to the scope of the queue
and exchange.
Please raise a JIRA. Bindings are scheduled to get some work soon
(probably 6.2).
Kind regards, Keith.
On 30 June 2016 at 09:55, Adel Boutros <ad...@live.com> wrote:
> Hello,
>
> In the definition of the fanout exchange[1], it is mentioned "The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key". However, using the web management console, when I create a fanout exchange, it forces me to set a binding key.
>
> I believe this is a bug. Do you agree or did I misunderstand something?
>
> Regards,
> Adel
>
> [1] https://qpid.apache.org/releases/qpid-java-6.0.3/java-broker/book/Java-Broker-Concepts-Exchanges.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org