...
My other focus this week was around an issue that has come up a couple of times regarding the updater in GSearch. In the default installation scenario GSearch is installed into the same Tomcat as Fedora, and Fedora starts the message broker on startup. Unfortunately, if the Tomcat server happens to start GSearch first, it's not able to connect to the message broker. To get around this the Fedora messaging client (which is used by GSearch) now spawns a thread to do the connection and performs several retries if the first attempt is not successful. This allows GSearch to let Fedora to start and get the broker going before connecting. As a side note, testing this out required using a separate Tomcat to run GSearch, so it verified the ability to run GSearch external to Fedora.