You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Shikhar (Jira)" <ji...@apache.org> on 2022/10/17 02:02:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17618371#comment-17618371 ]
Shikhar commented on AMQ-9123:
------------------------------
Hi. I am a beginner in open source. Will this be a good first issue for me to work on? If not, can someone suggest one to me to start contributing?
> 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
> 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)