[
https://issues.apache.org/jira/browse/AMQ-6798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140029#comment-16140029
]
ASF subversion and git services commented on AMQ-6798:
------------------------------------------------------
Commit eca72dc81ad8113e31fadf161580bf5e2b93e27a in activemq's branch
refs/heads/activemq-5.15.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=eca72dc ]
AMQ-6798 - Clean up store usage object on Queue stop
When queues are stopped the StoreUsage object needs to be stopped so it
will be removed from the parent StoreUsage. This allows the object to
be garbage collected and prevents a memory leak.
(cherry picked from commit 35bd3ad938f5c378b17a34980d2f3480bf3bbfc3)
> 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, 5.15.0
> 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
> Assignee: Christopher L. Shannon
> Fix For: 5.15.1, 5.16.0
>
> 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)
