Hi All, especially Richard Peter who was the original poster on this thread.

I've just posted about QMF2 support I've just implemented for the Java Broker via a ManagementPlugin.

Using this you can use qpid-config to control the Java Broker (note you need to be running a fairly recent version of the Java Broker and qpid-config, I've been using Qpid 0.20).

See

https://issues.apache.org/jira/browse/QPID-3675

HTH
Frase


On 10/02/13 12:58, Keith W wrote:
Hello Peter

Qpid-cli was removed some time ago (by QPID-3260).  At the point of
its removal, it had received no maintenance for a number of years and
has been omitted since 0.6 owing to problems affecting its release
artefacts. I doubt resurrection would be straightforward and I would
encourage more discussion on this list prior to any effort expended in
that direction.

The Java Broker has two management interfaces: JMX interface and a
web-management interface (which is backed by a RESTful API) both of
these interfaces could be used in a programmatic fashion from
monitoring scripts.  The JMX interface exposes the connections to the
Broker via org.apache.qpid.management.common.mbeans.ManagedConnection.
  Sessions within those connections are exposed by the
ManagedConnection#channels() operation.   Connections/sessions are not
yet exposed via the REST interface.

Kind regards, Keith.


On 8 February 2013 21:00, Richard Peter <[email protected]> wrote:
Lahiru,

Thanks for the quick response.  That would be soon enough for my time
tables.  I can continue development/testing without the CLI for now.  I
would need something within a month for me to integrate it with our current
monitoring scripts.  I'm considering expanding on the current JMX management
to allow monitoring of sessions.  This was available on the python
management side and we used it for traceability to track down specific
connections to queues/consumers and I would need to keep this functionality.



On 02/08/2013 02:22 PM, Lahiru Gunathilake wrote:
Hi Richard,

How urgent is this ? I can certainly have a look in to this week after
next
week, and fix the CLI for Java broker.


Regards
Lahiru

On Fri, Feb 8, 2013 at 3:00 PM, Richard
Peter<[email protected]>wrote:

We are in the process of switching from the C++ broker to the java
broker.
   Is there no CLI replacement for qpid-stat for the java broker?  Found
the
qpid-cli from 2008, but according to posts from Robbie in 2009 it hasn't
been maintained.  We use qpid-stat extensively for remote monitoring of
remote qpid brokers.

Thanks,

Richard Peter


------------------------------**------------------------------**---------
To unsubscribe, e-mail:
[email protected].**org<[email protected]>
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]

For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to