Consistent management names for connections in a cluster.
---------------------------------------------------------
Key: QPID-2403
URL: https://issues.apache.org/jira/browse/QPID-2403
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Clustering, Qpid Managment Framework
Affects Versions: 0.6
Reporter: Alan Conway
Assignee: Alan Conway
Management objects representing connections in a broker are named for the
remote end of the socket ip:port. In a cluster, a broker has normal connections
and "shadow" connections representing a connection on another broker. The
shadow connections are named "[shadow]ip:port" Management tools use this
convention to ignore shadow connections and display only the local connections
to a broker.
This is inconsistent with other management objects which are named identically
in all brokers, and the problem is compounded because connections are
containers for other objects (sessions, consumers) so inconsistency in the
connection name makes the names of all the children inconsistent.
Commit r907123 fixed this by making the connection names consistent and adding
a "shadow" property to the qmf Connection object. However this broke the Java
builds. This JIRA is to discuss what the correct solution should be that works
for both brokers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
