Ben,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><snip></div></div></blockquote>
<div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div>One strategy that springs to mind to turn the no_ack flag when sending the consume command to the broker. I will have to have a look to see what the behaviour of this, because I don't know off the top my head. Alternatively if you can detect the failure of a web site, can you actively cancel the subscription?</div>
</div></div></blockquote><div> </div><div>***** Actually, I believe I have turned off the no_ack flag and am actively sending acks when appropriate.:<br><br> BasicConsume = #'basic.consume'{<br> ticket = Ticket,<br>
queue = Qname,<br> consumer_tag = Tag,<br> no_local = false,<br> no_ack = false, % false -> keep msg in queue until consumer sends basic.ack ********<br> exclusive = true, % We only want one consumer ever on this queue<br>
nowait = false % We want to wait for a response from the server to this message<br> },<br><br>However, I must have done something wrong because RMQ continues to send even if I haven't acked.<br><br>As for canceling, that's exactly what I am doing, and that's what's crashing the channel :)<br>
<br>Ed<br></div></div><br>