Tim, Thanks for the quick response.
Regarding setting up and starting a full ActiveMQConnection: 1) No problem on the links, I appreciate the details. I was hoping to have something a little more lightweight than actually creating a connection and then closing it ... seems lie creating a new connection every second would put undo burden on the broker just to probe if the broker is listening on that port? Is there some other "trick" in openwire to make the probe more lightweight while still avoiding the error in the broker logs, e.g. just send something like a WIREFORMAT_INFO request? Regarding clients reconnecting after broker failover: 2) The F5 would only be used to route the initial connection request ... after that, my understanding is that as long as clients use the "failover" protocol when connecting to the VIP, e.g. something like "failover:(tcp://activemq-vip:61616)", and the broker-side transport connector has "updateClusterClients" and "rebalanceClusterClients" set to true, then the broker and client would exchange info about the network topology and clients would reconnect directly to active brokers should the initial connection fail. adam -- View this message in context: http://activemq.2283324.n4.nabble.com/how-to-probe-broker-s-openwire-port-from-an-F5-VIP-tp4716641p4716662.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
