<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div>Would it be possible for you to send us the full logs from a run where the problem manifests, please? My hope in asking this is that there are informative stanzas earlier in the output than the channel close error reports you've sent us.<br><br>Regards,<br> Tony<br></div></blockquote></div><br><div>Hi Tony,</div><div><br></div><div>Better than that, I have attached a ruby script to reproduce the issue... and the associated log.</div><div><br></div><div>To be more precise:</div><div>1. First I launched "<span class="Apple-style-span" style="font-family: 'Lucida Grande'; ">rabbitmq_issue.rb<span class="Apple-style-span" style="font-family: Helvetica; ">" script, but didn't reproduced the issue</span></span></div><div>2. So I launched "<span class="Apple-style-span" style="font-family: 'Lucida Grande'; ">rabbitmq_issue_2.rb<span class="Apple-style-span" style="font-family: Helvetica; ">" (durable queues / exchange with a persistant message), and this time I reproduced the issue</span></span></div><div>=> The result is in "<span class="Apple-style-span" style="font-family: 'Lucida Grande'; ">rabbitmq_issue_log.txt<span class="Apple-style-span" style="font-family: Helvetica; ">"</span></span></div><div><br></div><div>I will try tomorrow to upgrade Erlang (actually it takes hours to compile, and I'm tired).</div><div><br></div><div>Hope this helps,</div><div>Aymerick</div><div><br></div><div></div></body></html>