[
https://issues.apache.org/jira/browse/QPID-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612980#action_12612980
]
Ted Ross commented on QPID-1174:
--------------------------------
I am going to commit this feature to make it available to others even though
there are some issues that need to be addressed soon.
The new feature is sufficient to demonstrate the propagation of the management
schema and the propagation of property and statistic changes in managed objects
to management consoles like qpid-tool.
The following issues shall be addressed:
1) The agent does not function if it cannot establish a connection with the
broker. Also, it will throw an exception if the connection to the broker is
lost. The desired behavior is that the client will continually attempt to
connect to the broker if it is not connected.
2) There are some features in the API that are not yet implemented.
3) Routing of "method" and "get" calls to the agent is not yet implemented.
Until this is done, methods cannot be invoked on agent-resident management
objects.
4) qpid-tool does not yet handle the case where there is more than one version
of the schema for a particular class.
5) The "agent" object on the broker (which tracks attached agents) is not
cleaned up when an agent is disconnected.
> Remote Management Agent for management of external components
> -------------------------------------------------------------
>
> Key: QPID-1174
> URL: https://issues.apache.org/jira/browse/QPID-1174
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker, C++ Client, Qpid Examples
> Affects Versions: M3
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Fix For: M3
>
>
> The management framework used in the C++ broker is extensible. It currently
> allows broker plug-ins to be managed and with this new feature, can be used
> to manage remote components through an AMQP-client-based interface.
> This new feature includes:
> 1) A C++ implementation of the agent,
> 2) C++ broker support for the remote agent, and
> 3) An example program/reference-implementation that uses the agent API
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
