[
https://issues.apache.org/jira/browse/AMQ-9123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17619981#comment-17619981
]
Lucas Tétreault edited comment on AMQ-9123 at 10/19/22 4:23 AM:
----------------------------------------------------------------
BTW, I was able to get a clean build with all tests passing with the
collections being cleared
([https://github.com/apache/activemq/commit/691bd836e624478361716c4a4091895f9ab472d4|https://github.com/apache/activemq/commit/691bd836e624478361716c4a4091895f9ab472d4)])
so I suspect there won't be any problems with this.
was (Author: tetlucas):
BTW, I was able to get a clean build with all tests passing with the
collections being cleared
([https://github.com/apache/activemq/commit/691bd836e624478361716c4a4091895f9ab472d4)]
so I suspect there won't be any problems with this.
> 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)
