[ 
https://issues.apache.org/jira/browse/AMQ-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897379#comment-16897379
 ] 

Graeme Moss commented on AMQ-7102:
----------------------------------

Thanks.  Shame you can't backport the change to the set type (or the original 
change for this JIRA mentioned in the first comment above).  If it's in 5.16.0, 
that's not released yet is it?  Having either change in a version that is 
released soon would help us a lot.  Is it possible?

> 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
>
>
> 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
(v7.6.14#76016)

Reply via email to