[rabbitmq-discuss] memory leak rabbitmq 3.1.5
Simon MacMullen
simon at rabbitmq.com
Thu Sep 26 13:23:33 BST 2013
Please keep rabbitmq-discuss on CC.
So that shows 30 STOMP connection processes. Is that what you would
expect? Does that correspond with what you see in the management
connection listing? What about "lsof -i :61613"?
Cheers, Simon
On 26/09/2013 12:14PM, Santi Nuñez-Cacho wrote:
> This is the response:
>
> [root@ ~]# rabbitmqctl eval
> 'length(supervisor:which_children(rabbit_stomp_client_sup_sup)).'
> 30
> ...done.
> [root@ ~]#
>
>
> thank you very much
>
>
> On Thu, Sep 26, 2013 at 12:03 PM, Simon MacMullen <simon at rabbitmq.com
> <mailto:simon at rabbitmq.com>> wrote:
>
> On 26/09/2013 10:15AM, Santi Nuñez-Cacho wrote:
>
> I start disabling one by one the plugins and I come across with
> the most
> feasible candidate. Stomp.
>
> I disable stomp plugin and memory settle.
>
>
> Hmm. Odd. I'm certainly not aware of a memory leak in STOMP.
>
> Are you sure nothing is opening STOMP connections to your broker?
> Connections will only appear in mgmt when a CONNECT frame has been
> sent, so if something is just opening TCP sockets then they will not
> show up.
>
> What does
> $ rabbitmqctl eval
> 'length(supervisor:which___children(rabbit_stomp_client___sup_sup)).'
>
> say when the system is in this state?
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
>
>
--
Simon MacMullen
RabbitMQ, Pivotal
More information about the rabbitmq-discuss
mailing list