L.S.,

You could give things a try with ServiceMix 3.4.0 which comes with ActiveMQ
5.5.0 - http://servicemix.apache.org/downloads/servicemix-3.4.0.html
That should help us determine whether you're bumping into a bug in the
older ActiveMQ 5.3.0 version or if there's something else wrong here.


Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


On Mon, Jan 2, 2012 at 3:45 PM, Fibonacci <[email protected]> wrote:

> Hello everyone!
>
> We have an OutOfMemory issue with JMS messaging running on SMX 3.3.2 using
> ActiveMQ 5.3.0. We've done some profiling and it seems that OutOfMemory
> issue is caused by the growing number of ActiveMQTextMessage objects in the
> JVM. To illustrate, the number of objects increased by 265 000 just over
> the
> night. Our initial thoughts were that messages are not being acknowledged
> correctly, thus not being removed from the topics. Checking the problematic
> ActiveMQ topic statistics we got the following:
> DequeueCount = 307236
> MinEnqueueTime = 1
> MaxAuditDepth = 2048
> AverageEnqueueTime = 0.08459946100066398
> InFlightCount = 0
> MemoryLimit = 5242880
> Type = Topic
> EnqueueCount = 160886
> MaxEnqueueTime = 8
> MemoryUsagePortion = 0.0
> ProducerCount = 1
> UseCache = true
> MaxProducersToAudit = 32
> BrokerName = localhost
> ConsumerCount = 2
> ProducerFlowControl = false
> QueueSize = 160886
> MaxPageSize = 200
> MemoryPercentUsage = 0
> DispatchCount = 307236
> ExpiredCount = 0
>
> The following doesn't make sense:
> 1) DequeueCount = DispatchCount > EnqueueCount.
> 2) With that DequeueCount and DispatchCount, how can QueueSize still be >0?
>
> This would indicate that messages are consumed but not removed from the
> topics as they should be. We successfully receive all the messages on our
> consumers. On top of that our consumers have acknowledge policies set to
> AUTO_ACKNOWLEDGE. I found the JIRA bug report [AMQ-1600] which pretty much
> describes the behavior in case 2) but it states that the bug was resolved
> in
> version 5.3.0 - which is the one we are using. I already posted the problem
> on the
>
> http://activemq.2283324.n4.nabble.com/EnqueueCount-DequeueCount-DispatchCount-and-QueueSize-inconsistencies-in-5-3-0-bug-td4224696.html#a4253272
> ActiveMQ mailing list , and received an information that not all given
> statistics are applicable to the ActiveMQ topics in version 5.3.0, and/or
> some calculations might be incorrect. Unfortunately no other specifics were
> available.
>
> So if anyone has bumped into similar problem using ServiceMix 3.3.2 with
> ActiveMQ 5.3.0, I would be very grateful for any advice.
>
> --
> View this message in context:
> http://servicemix.396122.n5.nabble.com/OutOfMemory-problem-with-SMX-3-3-2-and-ActiveMQ-5-3-0-tp5114781p5114781.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

Reply via email to