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] Updated: (QPID-1284) QMan : Qpid JMX Management Bridge
Date Tue, 30 Sep 2008 07:31:44 GMT

     [ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrea Gazzarini updated QPID-1284:

    Attachment: qman_predefined_handlers_patch

Hi all,
submitted  patch (qman_predefined_handlers_patch) contains an update related to message handlers.
There are some handlers that need to be hard-coded because they are part of core engine (in
the previous version they were completely configurable). 
If those handlers are missing (and if they are configurable you can do that) QMan is not working.
So, at the moment, 'i', 'c' and 's' message handlers are hard-coded.
Improvements will be made in order to let the user to configure additional handlers for the
same opcodes ('i' for example). 
So the final situation will be something like this :

- QMan has a predefined set of handlers for each opcode;
- Using configuration, QMan administrator can configure additional handlers for the same opcode.
I think that those additional handlers will be used to work with "crosscutting" concerns 
specific for opcode (for example a debugging 'i' message handler);

I'm working on that...



> 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: actors.jpg, class_definition_building.jpg, commons-pool-1.4.jar,
DomainModel.jpg, estabilish_initial_connection.jpg, QMan.jar, qman_patch, qman_predefined_handlers_patch,
QpidClass.jpg, use_cases.jpg
> 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.

View raw message