You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/05/03 11:23:04 UTC

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

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

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

Commit c4a1346875dc40c1469e5b9625efe73eccb4b081 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c4a1346 ]

[AMQ-6465] fix up test interplay - clean on start and consume what is produced


> 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.15#6346)