Hi, Matt:<div><br></div><div>And Matthias roundly mocks me for my earlier flippant reply. �More correctly, your wireshark is watching traffic *to* the management port, but of course that traffic is not management traffic, it's Federation AMQP that's promptly encountering the HTTP response on the management port and understandably dying during the AMQP handshake... :-)<div>
<br></div><div>My bad!</div><div><br></div><div>Jerry</div><div><br><div class="gmail_quote">On Wed, Nov 14, 2012 at 1:51 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Matt,<div class="im"><br>
<br>
On 14/11/12 21:20, Matt Pietrek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
�> Err, 55672 is the HTTP management port. You want 5672, AMQP.<br>
<br>
True. I knew the difference between 5672 and 55672. I just figured<br>
federation had something to do with 55672 because that's the ONLY port I<br>
see traffic on between the two hosts.<br>
</blockquote>
<br></div>
You specified 55672 in your federation config. Unsurprisingly the federation AMQP client isn't going to have much joy trying to talk to the management port.<br>
<br>
Ditch the port setting and you'll hopefully have more luck (or at least get a different error in the logs).<br>
<br>
Regards,<br>
<br>
Matthias.<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div></div>