[rabbitmq-discuss] memory leak rabbitmq 3.1.5

[Santi Nuñez-Cacho]

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?

I got this:

    real_server XX.XX.XX.XX 61613 {
        weight 1
        TCP_CHECK {
            connect_timeout 2
            connect_port 61613
        }





On Mon, Sep 30, 2013 at 1:11 PM, Santi Nuñez-Cacho <brian.santiago at gmail.com
> wrote:

> In the same moment I stopped keepalived the memory stabilize.
>
> I attach the tcpdump output for 61613 port. ( it should be just keepalived
> connections from the other balanced
> server, as this cluster has no queues )
>
>
> On Fri, Sep 27, 2013 at 3:49 PM, Emile Joubert <emile at rabbitmq.com> wrote:
>
>>
>> Hi.
>>
>> On 26/09/13 15:18, Santi Nuñez-Cacho wrote:
>>
>> > =INFO REPORT==== 26-Sep-2013::16:12:46 ===
>> > accepting STOMP connection <0.19254.0> (XX:49217 -> YY:61613)
>> >
>> > =INFO REPORT==== 26-Sep-2013::16:12:46 ===
>> > closing STOMP connection <0.19254.0> (XX:49217 -> YY:61613)
>>
>> I've attempted to reproduce this problem from your description but did
>> not succeed. Can supply a network packet capture file of TCP traffic
>> between the broker and the load-balancer under the conditions that lead
>> to the leak? Tools such as tcpdump can create such a file.
>>
>>
>>
>>
>> -Emile
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131001/3fa005cf/attachment.htm>