[rabbitmq-discuss] RabbitMQ 1.6 persistence?

[Chris Wiegand]

We were trying out RabbitMQ (1.6, just downloaded it last week), and while it's throughput is great compared to ActiveMQ, I'm finding that if the erlang session dies (like say if I kill it, or try to pump in 1 million messages and it runs out of memory), and then I re-start the RabbitMQ server it takes a rather long time to load the persistence stuff, but then just clears out the queues, and the file (rabbit_persister.LOG) just gets truncated and the messages were not persisted.

Am I misunderstanding how RabbitMQ implements persistence? I expected that if the broker stops, and then gets relaunched that it would reload the last saved state for the queues, etc.., but that doesn't seem to be taking place. We're running it under Windows, under the most recent version of erlang (also just downloaded last week), in case that would affect anything. I'll try this under Linux and OpenSolaris here soon, in case that makes a difference.

I'm using the .Net bindings, and setting the BasicProperties' DeliveryMode to 2 for persistence, is there anything else I have to do to make a queue persist?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090714/8c84b37c/attachment.htm