Description of problem: If you follow the installation guide for the console including making sure there is a broker registered in the configuration file (cumin.conf) the broker remains absent from the Messaging tab. An event like qpid-stat triggers some sort of change event which allows cumin to see the broker on the console UI. BTW any change my require an update to the documentation. Perhaps not, but maybe. Version-Release number of selected component (if applicable): 1.3 How reproducible: Steps to Reproduce: Install MRG Messaging as per MRG Messaging Installation guide. Install the MRG Console as per the MRG Management Console Installation Guide. Start the broker Start the console Log into the console and go to the Messaging tab. There is no broker. Wait as long as you'd like. (I ran it for a weekend.) Then run qpid-stat -c Look at the console and see that the broker now shows up. 1. 2. 3. Actual results: Expected results: Additional info:
Note, this seems to be caused by a null value in the _systemRef_id field of the broker record in the postgres database. Starting up a console causes this value to be filled in.
Retested from scratch to make sure that no steps in install/config were missed. I'm still seeing the same problem.
Before 1.3 release, I was told the needed workaround will be mentioned in release notes. It probably wasn't. See bug 634975.
*** This bug has been marked as a duplicate of bug 634975 ***