Thanks, Ben.<br><br>Do you have any general suggestions as to how to recover cleanly from multiple connections dying in an application because the broker went down? Ideally, I'd like to be able to recover gracefully and not have to crash processes unnecessarily.<br>
<br>Regards,<br>Edwin<br><br><div class="gmail_quote">On Mon, Oct 27, 2008 at 8:04 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@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;">
Edwin,<br>
<div class="Ih2E3d"><br>
On Sun, Oct 26, 2008 at 5:55 PM, Edwin Fine<br>
<<a href="mailto:rabbitmq-discuss_efine@usa.net">rabbitmq-discuss_efine@usa.net</a>> wrote:<br>
> Should there be a handle_info clause for this in amqp_connection, or is it<br>
> something I need to code for somehow?<br>
<br>
</div>This is a bug in the amqp_connection module, it should be handling<br>
this message from the broker. I have started to fix this (19625<br>
refers), but I'm going to have to think about the event propagation.<br>
The current patch will at least handle the message.<br>
<br>
HTH,<br>
<font color="#888888"><br>
Ben<br>
<br>
</font></blockquote></div><br>