[rabbitmq-discuss] previous connection is NOT automatically closed if IP different

[L H, Wong]

I believe the port number shown on rabbitmq console (see below) is the
client port. This shows different IP and port is being used by the new
connection.

Consumers
Channel     Consumer tag     Ack required     Exclusive
210.19.225.88:36920 (1)     amq.ctag-ma8QOXnZ_UAK-
R7wddQGXA     ●     ○
210.19.225.3:60659 (1)     amq.ctag-igoa2WysTs79WAk969UFJg     ●     ○


I manage to reconnect from the same device on a different IP by
disconnecting from a Wifi router and connecting to another Wifi router. I
think this is a very common scenario including switching from 3G network to
Wifi network.

--Nick



On Mon, Nov 4, 2013 at 4:11 PM, Michael Klishin <mklishin at gopivotal.com>wrote:

> On nov 4, 2013, at 5:24 AM, L H, Wong <lhwong at gmail.com> wrote:
>
> > I am wondering why if IP for first and second connections are the same
> (in the scenarios in which the connection lost and resumed almost
> immediately via same network) the first connection gets closed almost
> immediately after the second connection was established.
>
> I don’t have an immediate answer but IP connections are not identified by
> IP’s. They are
> identified by a tuple of {protocol, client IP, client port, server IP,
> server port}.
>
> Unless Android tries to be smart and reuse ports in their TCP/IP stack
> implementation,
> client ports should be ephemeral (randomly taken from a pool of tens of
> thousands
> available ports).
>
> May I ask how you manage to reconnect from the same device on a different
> IP?
> --
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131104/c3b791be/attachment.htm>