You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org> on 2008/10/08 15:06:44 UTC
[jira] Updated: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Gazzarini updated QPID-1284:
-----------------------------------
Attachment: qman_test_cases_patch_08102008
qman_patch_08102008
Hi all, attached with this post you'll find the last patches of QMan. I submitted 2 patches :
- qman_patch_08102008 : QMan sources with additional features explained below;
- qman_test_cases_patch_08102008 : QMan test cases updated (see below).
Included in this patch (qman_patch_08102008) :
*** CONNECTION POOL LOGGING ***
- in DEBUG level you can see the lifecyle of each pooled connection.
*** METHOD INVOCATION ***
- Synchronous behavior (from external client perspective) of method invocation : QMan is handling as adapter between asynchronous nature of communication with broker and synchronous communication with external clients. So, at the end, method invocation for external client is synchronous
- Method invocation, in order to be able to return multiple values, is returning one of the following :
1) A result value object contaings output and bidirectional parameters (not schema ordered but this is not an issue because external clients knows nothing about QMan / QPid schema)
2) An exception (jmx MBeanException that wraps MethodInvocationException) when incoming code is not 0;
3) An exception (jmx ReflectionException that wraps NoSuchMethodException) when requested method is unknown.
*** TEST CASES ***
I've added another package called
org.apache.qpid.management.online
It contains (at the moment there's only one test) online tests. I mean, QMan must be up and running in order to run these tests.
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: actors.jpg, class_definition_building.jpg, commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, estabilish_initial_connection.jpg, message_processing.jpg, QMan.jar, qman_patch, qman_patch_08102008, qman_predefined_handlers_patch, qman_test_cases_patch, qman_test_cases_patch_08102008, 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.