You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/03/09 20:51:40 UTC
[jira] [Created] (AMQ-6204) Advisory broker does not properly
remove virtual consumer demand
Christopher L. Shannon created AMQ-6204:
-------------------------------------------
Summary: 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)