[
https://issues.apache.org/jira/browse/AMQ-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509347#comment-15509347
]
ASF subversion and git services commented on AMQ-6435:
------------------------------------------------------
Commit 5d9f1cd3d58cae626a53cd0fcf21656d4da38ca8 in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5d9f1cd ]
https://issues.apache.org/jira/browse/AMQ-6435 - use lesser guava dep to match
leveldb java
> 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)
