serious bug with Active MQ 4.0 non persistent broker

[Sanjiv Jivan]

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

[Sanjiv Jivan]

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

[James.Strachan]

Thanks for the heads up! :)

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
>

--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Sanjiv Jivan]

It might be a good idea to deploy the activemq 4.1 jars on the maven 2 repositories, all of which presently have 4.0.

http://repo1.maven.org/maven2/activemq/activemq-core/
http://mirrors.ibiblio.org/pub/mirrors/maven2/activemq/activemq-core/
http://static.springframework.org/maven2/activemq/activemq/4.0/

Sanjiv

On 2/9/07, James Strachan <james.strachan@...> wrote:

Thanks for the heads up! :)

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
>


--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

[Sanjiv Jivan]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Nevermind, I just found this note on the downloads link

"Note that until ActiveMQ graduates from the incubator, its jars are not allowed to be sync'd with the global maven repo."

On 2/13/07, Sanjiv Jivan <sanjiv.jivan@...> wrote:

It might be a good idea to deploy the activemq 4.1 jars on the maven 2 repositories, all of which presently have 4.0.

http://repo1.maven.org/maven2/activemq/activemq-core/
http://mirrors.ibiblio.org/pub/mirrors/maven2/activemq/activemq-core/
http://static.springframework.org/maven2/activemq/activemq/4.0/

Sanjiv

On 2/9/07, James Strachan <james.strachan@...> wrote:

Thanks for the heads up! :)

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
>


--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email