[
https://issues.apache.org/jira/browse/AMQ-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139936#comment-16139936
]
Anatolii Botov commented on AMQ-6798:
-------------------------------------
I suggest that org.apache.activemq.broker.region.Queue in method start() runs
StoreUsage like this:
if (systemUsage.getStoreUsage() != null) {
systemUsage.getStoreUsage().start();
}
But in method stop StoreUsage isn.t stoped. So it remains in its parent
StoreUsage.
Ok i'll try to test on 5.14.5 or 5.15.0.
> Queue left StoreUsage object in memory. Memory leak
> ---------------------------------------------------
>
> Key: AMQ-6798
> URL: https://issues.apache.org/jira/browse/AMQ-6798
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.10.2
> Environment: Linux 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24
> 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Anatolii Botov
> Attachments: 1535.dmp, activemq.xml
>
>
> Our services create queues on broker. It queues exists in 1 day then they
> become inactive, cause clients turned off. Active mq removes them by
> Inactivity timeout 60 seconds. But memory consumption of broker grows
> permanently. We acquired heap dump, and saw that
> org.apache.activemq.usage.StoreUsage contains 2.7 millions of object with 1.5
> gb. That objects belongs to StoreUsage of queues.
> I don't sure that we uses broker as it should be used. Maybe we shouldn't
> create new queues. But this behavior is stranged for me.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
