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

ASF subversion and git services commented on AMQ-6435:
------------------------------------------------------

Commit 6630e813795c20055b26cea52ba6a34390315bdf in activemq's branch 
refs/heads/master from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6630e81 ]

https://issues.apache.org/jira/browse/AMQ-6435 - destination mbean query api


> Implement JMX destination query API
> -----------------------------------
>
>                 Key: AMQ-6435
>                 URL: https://issues.apache.org/jira/browse/AMQ-6435
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.14.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.15.0
>
>
> In an environment when there thousands of destinations on the broker, current 
> way of exposing all MBeans and looking into them in the tools does not scale. 
> We need to implement an API that can be used by tools to filter, sort and 
> page destinations in this scenario.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to