[jira] [Resolved] (ARTEMIS-5672) Fix AddressManager Leaks

["Domenico Francesco Bruscino (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Domenico Francesco Bruscino resolved ARTEMIS-5672.
--------------------------------------------------
    Fix Version/s: 2.43.0
       Resolution: Fixed

> 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
>             Fix For: 2.43.0
>
>          Time Spent: 50m
>  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: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact