activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jok (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4814) Memory leak when unsubscribing durable consumer
Date Fri, 18 Oct 2013 08:25:51 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

jok updated AMQ-4814:
---------------------

    Description: 
When creating and closing durable subscribers, references to FilePendingMessageCursor in MemoryUsage.listeners
are not cleaned up.

The reason seems to be a missing call to FilePendingMessageCursor.destroy() in StoreDurableSubscriberCursor.stop().

A simple demo to reproduce the issue is attached (the leak is clearly visible after a few
hundred to thousand runs). Also, i have attached a patch which resolves this issue for me
- could someone check if this is correct?

  was:
When creating and closing durable subscribers, references to FilePendingMessageCursor in MemoryUsage.listeners
are not cleaned up.

The reason seems to be a missing call to FilePendingMessageCursor.destroy() in StoreDurableSubscriberCursor.stop().


> Memory leak when unsubscribing durable consumer
> -----------------------------------------------
>
>                 Key: AMQ-4814
>                 URL: https://issues.apache.org/jira/browse/AMQ-4814
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: jok
>              Labels: broker, durable_subscription, memory_leak
>         Attachments: DurableSubscriberLeakDemo.java, StoreDurableSubscriberCursor.diff
>
>
> When creating and closing durable subscribers, references to FilePendingMessageCursor
in MemoryUsage.listeners are not cleaned up.
> The reason seems to be a missing call to FilePendingMessageCursor.destroy() in StoreDurableSubscriberCursor.stop().
> A simple demo to reproduce the issue is attached (the leak is clearly visible after a
few hundred to thousand runs). Also, i have attached a patch which resolves this issue for
me - could someone check if this is correct?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message