[
https://issues.apache.org/jira/browse/AMQ-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581243#comment-16581243
]
ASF subversion and git services commented on AMQ-6465:
------------------------------------------------------
Commit 4a99103e706653f395e44d4b43a545b80ef664d9 in activemq's branch
refs/heads/activemq-5.15.x from gtully
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4a99103 ]
AMQ-7035 - use NonCachedMessageEvaluationContext in place of
MessageEvaluationContext to avoid unnecessary reference count management and
subsequent leaks. Rework AMQ-6465 with additional JMX related tests
(cherry picked from commit 50d27e7e545d30bc0d35f8dd8baf15b33522c33a)
> 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
> Priority: Major
> 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
(v7.6.3#76005)
