[rabbitmq-discuss] Workaround for basic reject...

Arun Suresh arun.suresh at gmail.com
Sun Jun 7 12:26:12 BST 2009


firstly, thanks for the quick response..

Why would closing the channel immediately not work? That will cause the <4
> outstanding messages to get requeued (and, if possible, delivered to other
> consumers), just like the message on which you encountered an error.

I was just trying to avoid exactly that situation.. basically i dont want
messages to be requeued untill I am sure the consumer has a problem while
processing them..

for the time being.. i have this workaround...
I have 5 Channels open on the consumer node (each with a prefetch of 1.. )..
so if the consumer has problem with any one message, I need to close just
that channel where the message came from... ofcourse, this would mean that
the message might get resent to another channel on the same consumer node...
but im still debating over whether thats a bad thing within the context of
our application...

do you think, generally speaking, this a good idea ?


oh..  and by the way.. does setting prefetch to 1 just the same as not using
basic.qos ??
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090607/c4813770/attachment.htm 

More information about the rabbitmq-discuss mailing list