[jira] [Commented] (AMQ-6465) Memory usage incorrectly increases when messages are forwarded over a bridge for a durable subscription

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575757#comment-15575757 ] 

ASF subversion and git services commented on AMQ-6465:
------------------------------------------------------

Commit b49df4848e81b58484644ab32f424b9c6bcb7243 in activemq's branch refs/heads/activemq-5.14.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b49df48 ]

https://issues.apache.org/jira/browse/AMQ-6465

Properly decrementing the message reference count in
DemandForwardingBridgeSupport when messages supression is checked for
durable subscriptions

(cherry picked from commit 406a34294befca4ba2de4b728c86f64b96a94945)


> Memory usage incorrectly increases when messages are forwarded over a bridge for a durable subscription
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6465
>                 URL: https://issues.apache.org/jira/browse/AMQ-6465
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, networkbridge
>    Affects Versions: 5.14.1
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.15.0, 5.14.2
>
>
> There is an issue with duplicate message suppression for durable subscriptions over a network bridge that is causing the memory usage counter to grow and never shrink.  The issue is that when the message is checked against the network bridge filter, a reference to the message is incremented (which increases the memory usage counter) but then that reference is never decremented so the memory usage doesn't decrease as it should.  The actual memory is freed but the counter continues to grow until it reaches the configured maximum at which point the broker can't do any work because it thinks the memory is full.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)