[rabbitmq-discuss] Published message not queued after publish-ok received when connection quickly closed
michael.s.klishin at gmail.com
Fri Jul 8 15:30:27 BST 2011
2011/7/8 Michael Klishin <michael.s.klishin at gmail.com>
> 2011/7/8 Michael Nacos <m.nacos at gmail.com>
>> so, what's currently the best way to publish messages consumed from one
>> queue into another with the amqp gem?
> Just republish them or take
Disregard this part. I now understand the question better. With a multi-step
workflow, when one application (A1) consumes messages from one queue,
processes them and publishes the original message or a different one to
another queue, you need to use a combination of features:
1. Explicit message acknowledgements
2. Publisher confirmations
The only way to know that your re-published message is received by the
broker is to receive an acknowledgement from it.
I now realize that documentation section does not provide any code examples.
I will put something together later today.
So A1 would consume a message, process it, republish it and as soon as
publishing confirmation arrives, A1 acknowledges the original one.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss