Hide Forgot
Unable to add multiple Brokers to the Messaging Console Description of problem: In v.1.2 there was a button on the Brokers tab under Messaging in the Management Console that allowed for a user to register new brokers. These brokers could be grouped within the Broker Groups and allowed for a user to setup a single management console that could connect with and show multiple brokers. This button, and functionality is not available ( at least not clearly ) in the 1.3 release. Version-Release number of selected component (if applicable): 1.3 Beta How reproducible: 100% Steps to Reproduce: 1. Start MRG Management Console - log in 2. Go to Messaging Tab 3. Go to Brokers Tab Actual results: A single broker ( / ) is shown. There is no button to add new brokers Expected results: A button to add brokers should be available. Additional info: The cumin.conf file does take a brokers list; this, it appears, is a comma seperated list or broker URI's, even with these specified only ONE shows up.
The brokers config parameter is the only mechanism in 1.3 for adding brokers. The mechanism that existed before was a big source of user confusion and implementation defects, because it conflated the two following concepts: * A broker that is just like other managed objects * A broker used internally for qmf communication The latter will always be configured via the brokers config parameter from here on out. A future version of qmf and broker management may support networks of brokers under management. In that case, you would not need to add another broker entry to the config parameter, one for one. Instead, just one would entry in the config parameter would be sufficient to discover all the managed qmf brokers in the network. In short, "Register broker" in the ui is not coming back. It was always a flawed idea before. Note that we don't have an "Add pool", etc., for grid. That's because those things are already discovered automatically. As to your last note, there is a bug preventing multiple brokers from working in the config file. More info to follow.
There's a serious data issue that causes db corruption when multiple brokers are configured. The problem is that broker agent ids are not unique. I have a fix that mangles these ids with extra information, but so far it is breaking db object references.
The db corruption is addressed in revision 4288. The fix does indeed mangle v1 object ids with extra info to avoid collisions. With this fix, multiple configured brokers should work properly.