agent registration and connection are two separate workflows. * agent can register with any server, if registration succeeds the result is that a failover list is sent down to the agent * agent uses failover list to make connection (see RHQ-671 for that work) ** connection is delayed until the server is "warmed up" (alerts cache loaded, etc)
rev1435 does the registration, then switches to primary. Still need to implement the "connect" message to warm up the server.
rev1447 now has the agent calling the server's connect method
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-703