Emile,<br><br>Thanks of the suggestions, one of the other people here noticed that their disconnects also occured at the same time as MS Outlook disconnects, so it seems to be a network issue.<br><br>Ill look up heartbeats.<br>
<br>thanks,<br><br>Tim<br><br><div class="gmail_quote">On Wed, Sep 14, 2011 at 11:22 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Tim,<br>
<br>
Op 13/09/11 00:56, het Tim Yen geskryf:<br>
<div class="im">> Hi,<br>
><br>
> Has anyone else run into this exception?<br>
<br>
</div>I'm unable to get the supplied code to produce the same exception. What<br>
versions of the client library and the broker are you using? Are there<br>
any relevant entries in the broker logfile at the time of the error?<br>
<br>
It should not be necessary to recycle connections. If the network<br>
infrastructure is causing timeouts then you should consider using AMQP<br>
heartbeats to prevent that.<br>
<br>
Another diagnostic test you could perform is to compare the output of<br>
"rabbitmqctl list_connections" on the broker with "netstat" on the client.<br>
<font color="#888888"><br>
<br>
-Emile<br>
</font></blockquote></div><br>