I dont believe they support anonymous relay, no. Since RabbitMQ is
primarily an AMQP 0-9-1 [with extensions] broker it still has the same
0-x broker model such as the 'exchange' and 'routing key' concepts, so
I'd expect you may be able to achieve something similar to the 1.0
anonymous-relay behaviour by sending to a particular address such it
represents a routing key on the default exchange.
However, there is no direct analogous support to 'create', since AMQP
1.0 is mainly a P2P message transfer protocol, it does not have the
same mandated broker model as AMQP 0-9-1 does and doesnt have explicit
exchange/queue declare methods which you were using previously. When
used with Qpid C++ broker, the old Qpid Messaging did have an
extension to allow it to mimic that behaviour when using AMQP 1.0, but
it doesnt work with any other broker or client that I am aware of.
Various AMQP 1.0 brokers support ways of auto-creation of queues etc
upon senders/receivers attaching to particular addresses, but I dont
know that RabbitMQ does. You may need to use its management interfaces
(often accessible using messages with the client, dont know in this
case) if you want to dynamically create/delete nodes.
On Tue, 11 Jul 2023 at 13:53, Tiaan Wessels <tiaanwess...@gmail.com> wrote:
>
> I use RabbitMQ and it seems the anonymous relay is not implemented. I asked
> on their forum and nobody answered. I tried it experimentally and it seems
> not to work. I originally wrote my AMQP s/w with Qpid Messaging and it did
> work as expected but moving to later flavors of Linux saw me trying to move
> to Qpid Proton and the former did not compile anymore on the newer Linux
> versions. I've also been advised some time ago on this mailing list to
> move to Qpid Proton. I am struggling to replicate some things from
> messaging though. Previously I'd pass create as sender options as per the
> docs
> >
> > Policies for automatically creating or deleting the node to which an
> > address refers.
>
> For instance, in the address string xoxox ; {create: always}, the queue
> > xoxox is created, if it does not exist, before the address is resolved.
>
> Against RabbitMQ this worked fine from my old s/w but with Qpid against the
> same broker i can't get something similar going. Maybe i should ask my
> original question differently: How can I replicate the 'create' in Qpid
> Proton ? Up till now I've both tried the 'To' anonymous relay approach and
> to create a new sender for each unique new address but neither seems to
> create the queue on the broker for me.
> Thanks
>
> On Wed, 5 Jul 2023 at 09:25, Robbie Gemmell <robbie.gemm...@gmail.com>
> wrote:
>
> > Assuming the server/broker you are using supports a fairly widely used
> > extension for 'anonymous relay', you can use this to create an
> > anonymous sender and convey the destination on the messages, by using
> > a null target "address" when opening the sender link, and then
> > ensuring the "to" field on the message Header section contains the
> > address you want the message to go to.
> >
> > You can alternatively have multiple senders open on the same session
> > at the same time (or different sessions) on the connection if just
> > varying within a constrained set of addresses.
> >
> > On Tue, 4 Jul 2023 at 19:48, Tiaan Wessels <tiaanwess...@gmail.com> wrote:
> > >
> > > Hi,
> > > How do i dynamically vary the address to which i send a message over the
> > > lifetime of a connection to a broker ?
> > > It seems i need to use the connection to create a new sender each time
> > and
> > > wait for on_sendable for the new sender ?
> > > If this is indeed the only way it would seem a bit cumbersome for high
> > > volume data being delivered to a range of addresses on a broker over the
> > > same connection.
> > > Thanks
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
