Hi Alex,
Some statistics have been there since the first release with the REST API -
version 0.18 in Sep 2012 (see
https://issues.apache.org/jira/browse/QPID-3998); and the mechanisms for
retrieving the statistics haven't fundamentally changed since version 0.28
in Jun 2014 (https://issues.apache.
Keith, quick follow up question. Any idea when the REST API was
introduced with the statistics getters?
On Mon, Oct 9, 2017 at 4:43 PM, Alex O'Ree wrote:
> Cool thanks
>
> On Oct 9, 2017 4:14 AM, "Keith W" wrote:
>>
>> Hi Alex
>>
>> The decision to deprecate the JMX interface in favour of a plat
Cool thanks
On Oct 9, 2017 4:14 AM, "Keith W" wrote:
> Hi Alex
>
> The decision to deprecate the JMX interface in favour of a platform
> neutral REST API was taken a few years ago. Support for JMX was
> finally removed with v6.1.
>
> The statistics (bytesIn, bytesOut and much more) are availab
Hi Alex
The decision to deprecate the JMX interface in favour of a platform
neutral REST API was taken a few years ago. Support for JMX was
finally removed with v6.1.
The statistics (bytesIn, bytesOut and much more) are available through
the REST API, but unfortunately the statistics were misse
Quick follow up question, I was poking around in the documentation
(hey nice theming!)
https://qpid.apache.org/releases/qpid-java-6.0.0/java-broker/book/Java-Broker-Management-Channel-REST-API.html
And saw that the JMX endpoint is going away eventually. Is this scheduled yet?
I also noticed that t
Sorry, hit send too quickly
if I uncomment
options.setManagementModeJmxPortOverride(9099);
it appears to have no affect on the JMX listener starting up.
Any recommendations on how to enable it programmatically?
using qpid version 6.0.0
On Sat, Oct 7, 2017 at 11:12 AM, Alex O'Ree wrote:
> H
Hello qpid community.
I have a product that integrates with Qpid and have happily been
running integration tests with it without much of a fuss. In the
past, I've written to this mailing list on how to attach qpid's java
server as a maven dependency and start it up programmatically in a
unit test