[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637935#action_12637935
]
Ted Ross commented on QPID-1284:
--------------------------------
Andrea,
QMan can be made to prevent closing its own connection and session. You will
need an enhancement to the API to do this however. I'm told this enhancement
is imminent.
With regard to exposing powerful methods to remote actors, the broker provides
an ACL capability to selectively allow or deny access to methods for specific
users.
-Ted
> 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.
