activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lionel Cons <>
Subject Feedback on Apollo's management interface
Date Tue, 17 May 2011 07:49:54 GMT

In order to be usable in large installations, the API should support
querying multiple objects in one request. This is not about aggregation,
it's about getting all the information in less HTTP requests. For instance,
for queues, the API could support:

  -> return the list of all queue statuses


  -> return the list of some queue statuses

Again for scalability reasons, it would be useful to be able to control the
amount of information retrieved. If one simply wants metrics information for
thousands of queues, he could request:


to get only the "id" and "metrics" fields of all the queue status objects.

FWIW, we currently heavily use these two features (multiple objects and
given attributes) when querying ActiveMQ'a JMX using the excellent jmx4perl

It seems that, by using the "json" suffix, one can get JSON data without
having to change the HTTP Accept header. See




If this trick is supported, it should be documented.

The queue status can contain producers with:


What is this "ref"? Is it the "id" of the connection?

IMHO, if yes, it should be renamed; if no, the "id" should be added to ease
cross referencing.



View raw message