[rabbitmq-discuss] redelivering message without loosing order
hpk.warrier at gmail.com
Sat Dec 10 17:33:54 GMT 2011
With the the basic queue based message consumption, I've this scenario ,
where my queue consumer reads message from queue and pass on as response to
remote application client. However as I may not get the message processing
response from client immediately, I'll not like to acknowledge message
while consuming from queue. In the event some issue occurs at the
application client and I need to resend the earlier message, how can i do
In my scenario I also need to take care that the message being re-requested
should follow the order. And I'm not sure whether basicRecover() is the
right way as I feel that it may put the content as the last entry in queue?
For eg: In my case first message send content which needs to be created
and the second one is update on the first message's content. For some
reason first message processing fails and client is not able to give
reject/acknowldege, the second one may not be requested at all. And when
the application client next connects it will get the second message which
will fail due to business logic [as first one is not available].
I was thinking if it is possible to send the first message again when the
client reconnects before giving the second message. Is it possible? Else
what is the alternative?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss