You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2008/03/06 15:30:35 UTC

[jira] Assigned: (AMQ-1199) provide a new simple API so end users can view available destinations and query them to find their statistics (such as queue depth etc)

     [ https://issues.apache.org/activemq/browse/AMQ-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan reassigned AMQ-1199:
-----------------------------------

    Assignee: James Strachan

> provide a new simple API so end users can view available destinations and query them to find their statistics (such as queue depth etc)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1199
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1199
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: James Strachan
>            Assignee: James Strachan
>             Fix For: 5.1.0
>
>
> From the dev list..
> On 3/9/07, Dhawan, Vikram (LNG-DAY) <vi...@lexisnexis.com> wrote:
> > Hi,
> > Is there a direct way using OpenWire Client API to get the number of
> > consumers attached to a Queue at a given point of time? I know it can be
> > done using JMX API but I was wondering if it can be done using Open Wire
> > client api.
> 4.2 has a command agent...
> http://activemq.apache.org/command-agent.html
> which can be used for sending simple text commands to the broker and getting replies - such as to enquire about queue depths and the like.
> There's also advisory messages...
> so you can listen to the operation of the broker, seeing new destinations, consumers, producers etc.
> However we've never yet wrapped up a little easy API folks can use on the client to easily view the available destinations and get their stats etc.
> Something like the following...
> {code}
> Collection<ActiveMQQueue> connection.findQueues()
> Collection<ActiveMQTopic> connection.findTopics()
> // look up stats like queue depth etc
> DestinationStats getDestinationStatistics(ActiveMQDestination);
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.