<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br><div><div>On 10 May 2013, at 13:56, Laing, Michael P. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div><div>Here's the config that is failing – there are a lot of substitution parameters as you can see, but the hostnames are explicit.</div></div></div></blockquote><br></div><div>Right - so this is indeed another instance of the problem reported at <a href="http://rabbitmq.1065348.n5.nabble.com/Shovels-not-reconnecting-with-RabbitMQ-3-1-0-td26372.html">http://rabbitmq.1065348.n5.nabble.com/Shovels-not-reconnecting-with-RabbitMQ-3-1-0-td26372.html</a> - because you don't set an explicit reconnect_delay, the shovel workers permanently halt once the first connection attempt fails, instead of restarting (after a slight delay) and trying again. As a temporary fix, you can add in the default reconnect_delay yourself, using {reconnect_delay, 5}. We will, as I said earlier, include the fix (which has already been merged) in the next service release.</div></div><div><br></div><div>Cheers,</div><div>Tim</div></body></html>