Dejan Bosanac resolved AMQ-6435.
    Resolution: Fixed

There's now two new methods on BrokerView

public String queryQueues(String filter, int page, int pageSize)
public String queryTopics(String filter, int page, int pageSize)

along with 

public CompositeData[] browseQueue(String queueName)

which should allow basic monitoring of the broker even when the all queue and 
topic mbeans have been suppressed like

{code} <managementContext>

The syntax of the filter and return is described more in JavaDoc of 

> 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

Reply via email to