<div dir="ltr">Very good point. I did ask that question in my previous email, but I don't think it has been answered yet.<br><br><div class="gmail_quote">On Fri, Sep 12, 2008 at 4:16 PM, tsuraan <span dir="ltr"><<a href="mailto:tsuraan@gmail.com">tsuraan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">> So it's a bit of a time bomb, but will not be the show-stopper I imagined,<br>
> because if the VM does crash for any reason, I will make sure it gets<br>
> restarted by a watchdog, so service won't be interrupted for long and nobody<br>
> besides myself and my client will know any better or even care. I'll also<br>
> have to make sure that my code notices that Rabbit died and reconnect when<br>
> it comes back up (which the code should be doing anyway). The worst that<br>
> will happen is that some in-flight messages that didn't make it to disk may<br>
> need to be re-sent.<br>
<br>
</div>If RabbitMQ crashes because it's out of memory, I understand that it<br>
should be able to start again without losing any data. Will the next<br>
message sent to it (before any messages are dequeued) cause the queue<br>
to crash again? I assume that must be the case, since nothing was<br>
lost when the program crashed. I don't know what to do about this,<br>
but it may be something to try to plan around.<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br>
</div></div></blockquote></div><br></div>