Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.6
-
None
Description
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.