[
https://issues.apache.org/jira/browse/AMQ-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187806#comment-15187806
]
ASF subversion and git services commented on AMQ-6204:
------------------------------------------------------
Commit 442fadac87a248cfe1efefd678b9fff6bd9f8733 in activemq's branch
refs/heads/activemq-5.13.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=442fada ]
https://issues.apache.org/jira/browse/AMQ-6204
Fixing the removal logic on virtual destination remove inside of
Advisory Broker to clean up virtual destination maps properly. Added a
test to verify. Also added new debug logging to help track down any
future issues.
(cherry picked from commit a2781e3966ded41a241d24ffb8d85d410c39eb21)
> Advisory broker does not properly remove virtual consumer demand
> ----------------------------------------------------------------
>
> Key: AMQ-6204
> URL: https://issues.apache.org/jira/browse/AMQ-6204
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.2
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
>
> When virtual destination network demand is enabled based on the existence of
> a destination ( the useVirtualDestSubsOnCreation flag as described in
> AMQ-6027) , there is a map called brokerConsumerDests that tracks the unique
> demand for the existence virtual destinations.
> Elements are not being properly removed from this map when a virtual
> destination is removed. All elements are being removed from this map instead
> of just the ones that match the removed virtual destination. This can cause
> entries in a different map (the virtualDestinationConsumers map) to not be
> cleaned up and for duplicates to be added if the virtual destination is
> re-added later. This can lead to a memory leak as this map can continue to
> grow and not be cleaned up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
