2011/7/26 Marek Majkowski <span dir="ltr"><<a href="mailto:majek04@gmail.com">majek04@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I suspect, the idea was to support automatic reconnections. But this<br>
is quite hard in AMQP world (that's a polite way of saying "impossible").<br></blockquote><div><br>It's not so bad actually. The application needs to know what to do when the connection comes back, of course, but automation of the connection lifecycle, with backoff etc and notification of the transitions between states is quite straightforward.<br>
�</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I wouldn't be surprised to hear that that feature was never finished.<br></blockquote><div><br>It was working OK way back at pika 0.5.x, but I think it might have slipped out of sync with the refactorings that have happened since. If you're interested, you can see a functional example of the use of automatic reconnections in a shovel-like tool at <a href="https://github.com/pika/pika/blob/ffac8a64c23e1d1e8aabacfefb91abc125d31375/examples/demo_relay.py">https://github.com/pika/pika/blob/ffac8a64c23e1d1e8aabacfefb91abc125d31375/examples/demo_relay.py</a>. That tool, once started, was able to cope with repeated broker restarts at either end.<br>
<br>Regards,<br>� Tony<br><br></div></div>