Any system monitoring tool would go with your case, even a remote one. The trick is: ActiveMQ (at least the recent versions, which are what I use) won't open the broker ports until it gets the lock on the database, so just by looking at where your port is open you can tell which server is working and which is not.
-- Questo messaggio è di carattere riservato ed è indirizzato esclusivamente al destinatario specificato. L'accesso, la divulgazione, la copia o la diffusione sono vietate a chiunque altro ai sensi delle normative vigenti, e possono costituire una violazione penale. Nel caso abbiate ricevuto questo messaggio per errore siete tenuti a cancellarlo immediatamente confermando al mittente, a mezzo e-mail, l'avvenuta cancellazione. (Legge Italiana 196/2003). 2014-10-01 13:45 GMT+02:00 bansalp <[email protected]>: > AMQGods Please help, > > I have a system which is using failover uri mechanism with master-slave > architecture (when primary runs, failover waits on lock and when failover > run primary wait on lock on kahadb). > > I need my clients to know when there is a problem with connection to > broker. > > Whenever primary goes down failover takes over and clients get connected to > failover broker. I want my clients to know that primary is down and > similarly when failover goes down my client should know about it. > > What is the recommended way to do it? > > Please help, I really need answer to this quickly. > > Thanks > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Notification-of-connection-down-between-broker-and-client-tp4686035.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
