[
https://issues.apache.org/jira/browse/AMQ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916765#comment-16916765
]
Graeme Moss commented on AMQ-7102:
----------------------------------
Just to confirm, I effectively backported this fix to our current version of
ActiveMQ (5.15.6) by hacking this field using reflection to use the
ConcurrentHashMap.KeySetView that your fix uses. We saw a massive improvement
in performance, e.g. one of our systems took 5 mins to restart instead of 35
mins, purely down to this change. Thanks again for backporting it to the next
fix version.
> managementContext suppressMBean filters registration but still tracks objects
> as registered in error
> ----------------------------------------------------------------------------------------------------
>
> Key: AMQ-7102
> URL: https://issues.apache.org/jira/browse/AMQ-7102
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 5.16.0, 5.15.10
>
>
> The suppressMbean feature could be better is we don't unnecessarily track the
> suppressed mbean registrations in out copy on write set.
> Under load, the additional work on add/remove this can be a significant
> burden.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
