[rabbitmq-discuss] Messages does not survive a RabbitMQ service restart

Thu Nov 28 18:06:08 GMT 2013

A key thing to remember, and an easy thing to forget, is that a publisher
confirm is only confirming that what you ASKED FOR has been done by the
broker and the scope of what's being knowledge depends on what you
demanded...

Also the "durable" and "persistent" verbiage, given that those sound like
near synonyms to most ears in most contexts, trips folks up all the time...

On Thu, Nov 28, 2013 at 9:36 AM, Marcos Torres <marcos.torres at gmail.com>wrote:

> Yep, i missed that part. I though initially that a message confirmation
> was enough to persists a message. Once I set the message properties as
> Simon suggested started working.
>
>
>
>
> On Thu, Nov 28, 2013 at 1:26 PM, Frank Shearar <frank.shearar at gmail.com>wrote:
>
>> On 28 November 2013 14:56, Marcos Torres <marcos.torres at gmail.com> wrote:
>> > Hi there.
>> >
>> > The messages stored in a durable queue doesn't survive a service restart
>> > (I'm using windows version of Rabbit).
>> > I'm using message confirmation, but clearly I need to do something else.
>>
>> A durable _queue_ means that the queue definition survives a reboot. A
>> _persistent message_ is stored on disk, and will still be there after
>> a reboot.
>>
>> frank
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131128/0d5b151b/attachment.html>