[
https://issues.apache.org/jira/browse/ARTEMIS-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ARTEMIS-5672:
------------------------------------
Labels: pull-request-available (was: )
> Fix AddressManager Leaks
> ------------------------
>
> Key: ARTEMIS-5672
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5672
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a client creates a multicast queue on a wildcard address (e.g. an MQTT
> client subscribing to {{#}}) and then sends a message to an address that
> matches the wildcard (e.g. {{foo}}) that gets auto-created then when the
> address is removed (e.g. via the {{ActiveMQServerControl#deleteAddress}}) the
> broker will leak an entry in two different internal maps. Eventually this
> data can accumulate and cause the broker to run out of memory.
> This is an unusual use-case because no bindings are ever explicitly created
> on the auto-created address and many, many such addresses are created and
> removed over the life-time of the broker.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
