<br><br><div class="gmail_quote">On Mon, Oct 27, 2008 at 11:06 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>
<br>
On Mon, Oct 27, 2008 at 2:06 PM, Edwin Fine<br>
<div class="Ih2E3d"><<a href="mailto:rabbitmq-discuss_efine@usa.net">rabbitmq-discuss_efine@usa.net</a>> wrote:<br>
</div><div class="Ih2E3d">> Do you have any general suggestions as to how to recover cleanly from<br>
> multiple connections dying in an application because the broker went down?<br>
> Ideally, I'd like to be able to recover gracefully and not have to crash<br>
> processes unnecessarily.<br>
<br>
</div>When you say multiple connections in an application, are you referring<br>
to multiple TCP connections or multiple AMQP channels?</blockquote><div> </div><div>Both, actually. I have a connection pool of TCP connections to a rabbit broker, each connection of which supports multiple channels. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Valentino started a thread on a related topic so he may be able to<br>
chime in here: <a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2008-October/002105.html" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2008-October/002105.html</a><br>
</blockquote><div><br>I'll take a look.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I'm not quite sure whether the discussion was about how to supervise<br>
client connections using an OTP tree or whether I had that discussion<br>
with somebody else.....if it was, could that person please chip in<br>
here?<br>
<br>
HTH,<br>
<font color="#888888"><br>
Ben<br>
<br>
</font></blockquote></div><br>