We are going to use the active/passive mode of operation along with Berkeley DB to support our high availability design. On top of that, we were thinking of using Redhat Cluster software to monitor the two machines and assign a virtual IP to whichever machine is the true "active". In your Java Broker High Availability documentation, a footnote states "The automatic failover feature is available only for AMQP connections from the Java client. Management connections (JMX) do not current offer this feature". Is this only when a broker list is passed during the connection process? If we passed in one virtual IP when the connetion is created, it seems that Qpid would reconnect to the virtual IP once Redhat Cluster software detected the failover. Does this sound correct?Will this design work or should we implement something different? Also, is there a good example of C++ client code that would automatically reconnect? We currently have logic to catch exceptions and reconnect based on these exceptions, but we were thinking it would be cleaner if we could use the reconnect logic that Qpid supports.
-- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-High-Availability-Documentation-and-C-clients-tp7594781.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
