[rabbitmq-discuss] memory leak rabbitmq 3.1.5

[Emile Joubert]

Hi,

On 01/10/13 08:56, Santi Nuñez-Cacho wrote:
> I disable TCP_CHECK on keepalived configuration and the memory stabilized.
> @emile, do you use a specific configuration of keepalived that would
> bypass this problem?

Thanks for the network packet capture. This showed that connections are
being forced closed using TCP resets. I've managed to reproduce the
issue and a fix will follow shortly. STOMP is the only protocol
supported by RabbitMQ affected by this issue.

A workaround in the meantime would be to use a configurations that does
not close the network connections by resetting.



-Emile