qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Gazzarini (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
Date Tue, 23 Sep 2008 07:06:44 GMT

    [ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633634#action_12633634
] 

Andrea Gazzarini commented on QPID-1284:
----------------------------------------

Hi Ted, thanks for reply...now It's clear.

In a previous post you told me that "Other protocol updates have occurred in the method and
event area but those don't yet affect you (yet). "..well I've implemented method invocation;
I mean, QMan is able to see and invoke the broker exposed operations but the 'm' response
messages contain an error status code. 
Here are some examples :  


1) Invoking close() operation on a connection object instance. 

Status code : 4
Status text : InvalidParameter

2) Invoking solicitAck() on a session object instance.

Status code : 1
Status text :  UnknownObject

3) Invoking detach() on a session object instance.

Status code : 4
Status text : InvalidParameter

4) purge(int request)  on queue object instance with 0 as parameter value

Status code : 4
Status text : InvalidParameter

Where could I read those protocol updates?

Let me know.

Regards,
Andrea

> QMan : Qpid JMX Management Bridge
> ---------------------------------
>
>                 Key: QPID-1284
>                 URL: https://issues.apache.org/jira/browse/QPID-1284
>             Project: Qpid
>          Issue Type: New Feature
>    Affects Versions: M3
>         Environment: J2SE 5, any OS that is supporting Java
>            Reporter: Andrea Gazzarini
>         Attachments: DomainModel.jpg, QMan.jar
>
>
> QMan is an application used for exposing via JMX the management domain model of one or
more remote brokers.
> Capabilities (the list is not complete) : 
> - Operates from a formally defined management schema;
> - Uses the AMQP protocol and its type system for communicating with remote brokers;
> - Exposes via JMX the remote broker domain model: that means for each connected broker
QMan lets you see its domain model entities according to their schema (attribute, methods,
statistics and events). In addition, lets you invoke operations on those entities.  
> - Multi broker management; 
> - It doesn't have prior knowledge of the management model of the system under management.
no definition is hard-coded and entity definitions (schema) are requested and built "on demand";
> - Namespace separation between brokers : each connected broker can have a different schema.

> - JMX interface : QMan is itself a Management Bean and using JMX it exposes its public
interface (for example, to connect with a new broker). So at the end it should be exposed
via WS-DM, SMTP, RMI, etc...
>       

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


Mime
View raw message