On 09/09/2013 11:56 AM, sparso wrote:
I'm also seeing this problem. I changed the "example" to send 2,000,000
messages and added a usleep to the producer, and it leaks memory in version
3.7.1 and 3.8.0. Version 3.4.4 does not.
I will attempt to debug the problem (but I'm not familiar with the activemq
code). It does appear to be just the consumer that is leaking memory.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Memory-leak-in-activemq-cpp-activemq-cpp-library-3-7-1-tp4671248p4671306.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Are you sure its a memory leak, or is it just working as it should.
Depends somewhat on how you are using the client, if you are using
failover then there is a chance its just the Message Audit and
Connection State Tracker growing as the consumer is running tracking
messages to filter duplicates etc. You should try changing connection
parameters to narrow it down, otherwise who knows where to start looking.
1. try with and without failover
2. when using failover try turning off message audit.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
[email protected] | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
