[rabbitmq-discuss] memory leak rabbitmq 3.1.5
brian.santiago at gmail.com
Tue Oct 1 15:57:09 BST 2013
I changed the keepalived tcp_check by other type called misc_check ( a
check that can be done by yourself )
This check close the connection ( a simple nc execution ) , and everything
start to work again. And the memory stop growing and got stabilized.
On Tue, Oct 1, 2013 at 11:01 AM, Emile Joubert <emile at rabbitmq.com> wrote:
> On 01/10/13 08:56, Santi Nuñez-Cacho wrote:
> > I disable TCP_CHECK on keepalived configuration and the memory
> > @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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss