[rabbitmq-discuss] Management Plugin stops gathering stats ?

Simon MacMullen simon at rabbitmq.com
Thu Aug 25 18:27:13 BST 2011

On 25/08/11 18:12, Rene Parra wrote:
> The publish rates seem to only work if I use the CachingConnectionFactory in
> Spring vs the SingleConnectionFactory. Makes sense, because when I use
> SingleConnectionFactory, my publisher is creating and closing a connection
> on every single publish.... therefore rabbit only can create statistics for
> a connection that no longer exists (wouldn't make sense unless you are doing
> historic stats, which I'd be surprised if you do).

Ah, that makes sense. Yes, we want to do historical stats at some point, 
but we don't now.

> The stats bug, and the memory bug seem to be better in 2.5.1/R14B03. We are
> progressing with our soak / load tests at a very light load (100 TPS).
> I was able to exhibit the stats bug, and hence memory bug however in
> 2.5.1/R14B03 under high load.
> The video is here:
> TimePoints:
> * @ 0m00s:  - Memory Pressure WORKING, Throttling ACTIVE
> * @ 0m37s:  - BANG! Statistics stop collecting
> * @ 0m56s:  - Showing how Memory Level now exceeded.
> Good news is all the messages were indeed delivered.
> Bad news even after the test completed, I had to restart RabbitMQ to recover
> the memory back down to a normal state and get the stats/memory
> level/publish throttling working again.

Thanks. Looking at the logs for the previous run I now see that the 
process within mgmt that actually keeps track of memory use crashed at 
around this point, so it's possible that mgmt is no longer reporting the 
memory use accurately. So that's a bug.

Anyway, I think I now have enough information to make a better go of 
replicating this, which I'll do tomorrow. Thanks for the information.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list