You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2022/10/19 04:18:00 UTC

[jira] [Assigned] (AMQ-9123) ManagedRegionBroker should clear its various caches when stopped

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

Jean-Baptiste Onofré reassigned AMQ-9123:
-----------------------------------------

    Assignee: Jean-Baptiste Onofré

> ManagedRegionBroker should clear its various caches when stopped
> ----------------------------------------------------------------
>
>                 Key: AMQ-9123
>                 URL: https://issues.apache.org/jira/browse/AMQ-9123
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 5.17.2
>            Reporter: Lucas Tétreault
>            Assignee: Jean-Baptiste Onofré
>            Priority: Trivial
>
> Matt noticed that when ManagedRegionBroker is stopped only the registered mbeans are cleaned up but the various collections that hold queues, topics, subscribers, etc. are never cleared. Therefore, if a broker is stopped and started the caches will have previous run data in them.
> This code appears to have been this way since 2006 but we should likely clean up the collections when the broker is stopped assuming there are no intended side-effects in leaving them with previous run data.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)