Hi Simon,<br><br>We are currently using non-ssl ports, and only one-way federation in our
system. It seems that the whole thing is more stable now. However, the hanging still happened last weekend. Is there anything from our end that could help you pinpoint what the problem is? Logs or coredumps? <br><br>Cheers,<br>
<br>Brian<br><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 11:14 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06/03/12 22:57, Brian Jing wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Simon,<br>
<br>
We are using Erlang R14B04 on these servers.<br>
<br>
Our network is usually saturated by RabbitMQ traffic, probably partly<br>
because we don't have enough bandwidth, and partly because we've been<br>
using federation the wrong way (using same exchange for both up and<br>
downstream transfer). Not sure whether this could contribute to the<br>
issue. However, even if something bad happens with the network, isn't<br>
rabbit supposed to recover itself no matter what?<br>
</blockquote>
<br></div>
Yes, absolutely. And in my tests it does. But I'm not absolutely sure what is happening in your case; it seems to be something slightly less obvious than just dropping the network connection.<div class="HOEnZb"><div class="h5">
<br>
<br>
Cheers, Simon<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</div></div></blockquote></div><br>