[ 
https://issues.apache.org/jira/browse/ARTEMIS-5672?focusedWorklogId=983997&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-983997
 ]

ASF GitHub Bot logged work on ARTEMIS-5672:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Sep/25 14:54
            Start Date: 22/Sep/25 14:54
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on PR #5929:
URL: 
https://github.com/apache/activemq-artemis/pull/5929#issuecomment-3319552325

   @brusdev, I added it back with a small adjustment so it would pass. 




Issue Time Tracking
-------------------

    Worklog Id:     (was: 983997)
    Time Spent: 40m  (was: 0.5h)

> 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: 40m
>  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


Reply via email to