[rabbitmq-discuss] configuring rabbit-mq server to send back a publisher confirm after N messages.

Francesco Mazzoli francesco at rabbitmq.com
Tue Jul 24 10:54:15 BST 2012

At Tue, 24 Jul 2012 10:17:27 +0100,
Francesco Mazzoli wrote:
> At Mon, 23 Jul 2012 12:11:37 -0700 (PDT),
> rohit prasad wrote:
> > I am using Publisher-confirms.
> > Is there any way to tell Rabbit server to send a pub-confirm after N messages.
> > 
> > If this is possible, then in my rabbit client , I can wait for a pub-confirm
> > after sending N messages, and be sure that Rabbit server will send me a
> > confirm (ack or nack) pretty soon.  Otherwise the waiting time for the
> > pub-confirm becomes kind of undeterministic, we keep waiting till Rabbit feels
> > like sending a confirmation. Is this configurable in any way? Or Do you
> > suggest some other way to reduce the wait time for publisher-confirm acks?
> I'm not sure I understand what you are saying (especially the part about
> determinism), [...]

It occurred to me that the comment on non-determinism might refer to the fact
that you don't have strong guarantees about the confirms (they might not reach
their target, they might arrive in bulk or not, etc.).

However, if your goal is to publish a series of messages and have the certainty
that they all reached the broker in that order, you can use AMQP transactions,
which provide you the tools to have that guarantees (and more).  However, be
aware that transactions will greatly decrease throughput. See
http://www.rabbitmq.com/amqp-0-9-1-reference.html#class.tx for more information.

Francesco * Often in error, never in doubt

More information about the rabbitmq-discuss mailing list