Reconnect to topic queue via qpid-proton AMQP1.0

[Thomas Kettenbach]

Hi all,

we're using RabbitMQ (currently using version 3.9.12) as a messaging broker and connect several clients via AMQP1.0 protocol. Some publisher process is pushing arbitrary messages to several topics. When a client program is connecting to a specific topic, then RabbitMQ is generating a random name for the queue being used for this distinct connection. The following resource naming scheme is used: "topic" / RK (as specified in the amqp1.0 plugins documentation [1]

However, after a connection abort, i can't see a way to reconnect to the already existing queue using the queue-name of the last successful connection and consume messages that haven't been delivered because of the lost connection.

Is there a way to reconnect to this specific random queue name after a connection abort? I am not sure if i am on the right track here, so any other information is very much appreciated.

BR,

Thomas Kettenbach

--

[1]

https://github.com/rabbitmq/rabbitmq-server/tree/master/deps/rabbitmq_amqp1_0#routing-and-addressing

[Thomas Kettenbach]

Hi all,

i'd like to add some example to my question.

I'm using qpid-proton python examples: simple_recv.py [1] and simple_send.py [2]

receiver accepts 3 messages:

PN_TRACE_FRM=1 python simple_recv.py -a amqp://guest:guest@localhost//topic/foo -m 3

sender sends 6 messages:

PN_TRACE_FRM=1 python simple_send.py -a amqp://guest:guest@localhost//topic/foo -m 6

How can another receiver process retrieve the remaining 3 messages from the the '/topic/foo'?

The logfile: simple-recv1.txt seem to notify about releasing the last three messages via 'state=@released', does this mean, that those messages are lost?

BR,

Thomas

[1] https://qpid.apache.org/releases/qpid-proton-0.36.0/proton/python/examples/simple_recv.py.html

[2] https://qpid.apache.org/releases/qpid-proton-0.36.0/proton/python/examples/simple_send.py.html