[rabbitmq-discuss] memory leak rabbitmq 3.1.5

[Simon MacMullen]

Cool!

And this should be fixed in tonight's nightly build BTW.

Cheers, Simon

On 01/10/13 15:57, Santi Nuñez-Cacho wrote:
> 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
> <mailto:emile at rabbitmq.com>> wrote:
>
>
>     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
>
>
>
>
>


-- 
Simon MacMullen
RabbitMQ, Pivotal