<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 3, 2013 at 8:10 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This cleared that connection. The really weird thing is that lsof only<br>
shows that connection on the server, not on the client. I.e. I could<br>
find this on the server:<br>
</blockquote>
<br></div>
Hmm. That's very suspicious.<br>
<br>
So this is a very different scenario to the known issue I initially suggested. These connections really are there from the point of view of the server. If lsof is giving contradictory results on client vs server then that implies the problem is at a TCP level rather than AMQP.<br>
</blockquote><div><br></div><div style>Yes, they are indeed there on the server. It makes no sense to me how they can be, while not being on the server. I find it hard to believe myself.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Could there be a firewall or something which is interfering with the way TCP connections are torn down?</blockquote></div><br>It's running on Amazon EC2, so who knows. But now that I think of it I should probably take it up with them, maybe that's where the issue really is. But since there's no IPv6 support on Amazon, we should probably just disable it altogether and that might take care of the issue.</div>
</div>