« Return to Thread: serious bug with Active MQ 4.0 non persistent broker

Re: serious bug with Active MQ 4.0 non persistent broker

by Sanjiv Jivan :: Rate this Message:

Reply to Author | View in Thread

Some parts of this message have been removed. Learn more about Nabble's security policy.
For those interested, here are all the nitty gritty details :
 
http://jroller.com/page/sjivan?entry=profiling_a_jvm_embedded_in


 
On 1/23/07, Sanjiv Jivan <sanjiv.jivan@...> wrote:
Just a fyi that there's a serious bug with Active MQ 4.0 when configured with persistent="false".

I am using Lingo with Active MQ and basically the messages are not being removed from memory. In my case the size of the message was ~35MB and this resulted in a leak of 70MB. When the broker is configured with persistent="false", it uses a MemoryMessageStore which held on to an object of the message size at two places.
See the memory profile here :
http://www.jroller.com/resources/s/sjivan/lingo-amq-leak.jpg

Note that I did run the app under a profiler and also forced garbage collection which did reclaim a bunch of memory not not the 70MB help in the MemoryMessageStore. Sending the message again resulted in a total leak of 140MB and this behavior was consistent.

Fortunately this bug seems to have been fixed in Active MQ 4.1 so I strongly suggest that you upgrade if you're still on Active MQ 4.0.

Profile using Active MQ 4.1
http://www.jroller.com/resources/s/sjivan/ling0-amq-4.1.jpg

Sanjiv

 « Return to Thread: serious bug with Active MQ 4.0 non persistent broker

LightInTheBox - Buy quality products at wholesale price