<div dir="ltr"><div><div>Hi there.<br><br></div>The messages stored in a durable queue doesn't survive a service restart (I'm using windows version of Rabbit).<br></div><div>I'm using message confirmation, but clearly I need to do something else.<br>
<br></div><div>This is how I'm publishing the messages : <br><br>                using (var channel = rabbitConnection.Connection.CreateModel())<br>                {<br>                    channel.ConfirmSelect(); //enable confirms on channel<br>
                    foreach (var message in messages)<br>                    {<br>                        var serialization = _serializer.Serialize(message , Encoding.UTF8);<br>                        channel.BasicPublish(rabbitAddress.Name, string.Empty, null, serialization);<br>
                    }<br>                    channel.WaitForConfirms();<br>                }<br><br><br></div><div>In the RabbitMQ Management I see the confirmation throughput and the messages stored in ready state, but once the messages are there and then I stop the RabbitMQ service, when I start the service again everything is gone.<br>
<br></div><div>For reference I'm using this: <a href="http://www.rabbitmq.com/blog/2011/02/10/introducing-publisher-confirms/">http://www.rabbitmq.com/blog/2011/02/10/introducing-publisher-confirms/</a> and  <a href="http://hg.rabbitmq.com/rabbitmq-java-client/file/default/test/src/com/rabbitmq/examples/ConfirmDontLoseMessages.java">http://hg.rabbitmq.com/rabbitmq-java-client/file/default/test/src/com/rabbitmq/examples/ConfirmDontLoseMessages.java</a> although I use C# . I would like to know what I'm doing wrong.<br>
<br></div><div>I´m using RabbitMQ 3.1.5, <acronym class="" title="Erlang R16B01 (erts-5.10.2) [smp:4:4] [async-threads:30]">Erlang R16B01</acronym></div><div><br></div><div>From my understanding the consumer has nothing to do with persistance. Is this correct?<br>
<br></div><div>Thanks a lot in advance.</div></div>