On 12/15/2015 08:30 PM, cuneyt wrote: > After deleting kahadb files and restarting activemq 5.8, memory consumption > hits 72%, 61% of which is used by JmxMBeanServer > <http://activemq.2283324.n4.nabble.com/file/n4705033/amq-users-forum.png> > > QueueProducers MBean have entries similar to below: > brokerName=localhost,clientId=ID_dc01-repo-Tmp-01-60150-1441116374679-2_1,destinationName=rcoloderuploads3.response,destinationType=Queue,endpoint=Producer,producerId=ID_dc01-repo-Tmp-01-60150-1441116374679-3_1_1_1652,type=Broker > > And there are 678K of them accumulated over just 3 minutes. > > Having kahadb all cleared, and not seeing any activity on the web console > where can these MBean entries be coming from? > > Thanks for any pointers > Cuneyt > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/big-memory-jump-after-restart-tp4705033.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > There's a ton of fixes that have gone into the broker since 5.8 which was release several years ago at this point. You might want to give a later release a spin. You can of course troll through the jira entries for each release since then to see if any sound applicable.
-- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
