Hi Simon,<br><br>We are using Erlang R14B04 on these servers. <br><br>Our network is usually saturated by RabbitMQ traffic, probably partly because we don't have enough bandwidth, and partly because we've been using federation the wrong way (using same exchange for both up and downstream transfer). Not sure whether this could contribute to the issue. However, even if something bad happens with the network, isn't rabbit supposed to recover itself no matter what?<br>
<br>Thanks,<br><br>Brian<br><br><div class="gmail_quote">On Tue, Mar 6, 2012 at 10:44 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 11:01, Simon MacMullen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What's odd is that you are seeing ehostunreach after a connection has<br>
been up and running for some time, so I'd be curious to know if<br>
something is up with your network.<br>
</blockquote>
<br></div>
So I couldn't replicate the ehostunreach problem in the obvious way (taking down networking with an active SSL connection). However, I could get rabbit to hang on shutdown after killing a running SSL process - but only when running on older Erlang (R13B0x) - which version are you using?<div class="HOEnZb">
<div class="h5"><br>
<br>
Cheers, Simon<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</div></div></blockquote></div><br>