[rabbitmq-discuss] Dead but still established connections in RabbitMQ on EC2

[majek04]

On Wed, Feb 3, 2010 at 09:50, Mathias Meyer <meyer at paperplanes.de> wrote:
> [..] Some time after the client connected its host got
> a new (elastic) IP address assigned. One of the two active connections
> from the old IP was dropped as Rabbit received an according exception
> on it, but the other wasn't, and is still established according to
> lsof -i and netstat almost 24 hours later.

Mathias,

from what you say it appears as a TCP/IP layer issue.
Please play with keepalives on AMQP or TCP/IP layer,
and tell us if that solves the problem.

Cheers,
   Marek Majkowski