[rabbitmq-discuss] Possible memory leak in the management plugin

Pavel pmaisenovich at blizzard.com
Tue Jul 15 21:29:49 BST 2014

Last night I've run another test to confirm the results: at 200/s publish
rate with 700 channels/699 queues 3.1.5 crashed in ~4 hours (test ended with
java.net.SocketException: Broken pipe), 3.3.4 continued to run after ~20
hours with agg_stats table stabilized at a bit higher mark (comparing to
last test). Test results attached.


Simon MacMullen-2 wrote
> If running this test is not a huge effort for you, it might also be worth
> doing so against a nightly build - nightly builds disable detailed message
> stats by default, which should save a great deal of memory in your case.

Running test is trivial, it's just the environment that needs to be setup.
That said, wouldn't it be same as running 3.3.4 with
{rabbitmq_management_agent, [{force_fine_statistics, false}]} setting? We've
been using it in production since the issue with aggregated_stats table
growth was first discovered and the purpose of this test is to prove that
it's fixed now, so we can turn the detailed stats ON again.

*Thanks for the help troubleshooting this issue and quick fix in 3.3.1,

View this message in context: http://rabbitmq.1065348.n5.nabble.com/Possible-memory-leak-in-the-management-plugin-tp27414p36809.html
Sent from the RabbitMQ mailing list archive at Nabble.com.

More information about the rabbitmq-discuss mailing list