[rabbitmq-discuss] |Spam| Re: Possible memory leak in the management plugin
tmehlinger at gmail.com
Wed Jun 19 15:30:49 BST 2013
We aren't doing anything like that. Whenever one of our services starts
(which are based on Kombu, if that helps), it plucks a connection from its
internal pool, creates a channel on that connection, then binds on its
request queue, which hangs around until the service stops. The only thing
that deviates from this pattern is our monitor, which connects and
disconnects fairly rapidly, and uses exclusive queues.
That said, it's entirely possible that we have something floating around
that I don't know about that fits the behavior you described. I'll keep
digging and see what I can turn up. In the meantime, let me know if there's
any more information I can collect from Rabbit.
On Wed, Jun 19, 2013 at 6:13 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 18/06/13 16:11, Travis Mehlinger wrote:
>> We declare those queues as exclusive so they're getting cleaned up
> I have found a plausible candidate for the leak. But it's dependent on
> having a long lived channel which declares and deletes lots of short-lived
> queues. We keep some information on the deleted queues until the channel is
> closed. Could your monitoring tool be doing that? Obviously it would have
> to be deleting queues explicitly, not relying on them being exclusive.
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, Pivotal
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss