activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Basmajian, Raffi" <rbasmaj...@ofiglobal.com>
Subject RE: 5.12.1 Master/Slave behavior
Date Thu, 03 Dec 2015 20:01:39 GMT
Yes, that is expected behavior. Slaves do not service normal requests, the transport connectors
are not enabled, 

-----Original Message-----
From: Rallavagu [mailto:rallavagu@gmail.com] 
Sent: Thursday, December 03, 2015 1:57 PM
To: users@activemq.apache.org
Subject: 5.12.1 Master/Slave behavior [ EXTERNAL ]

All,

I have setup a Master/Slave cluster on a single machine by creating two broker instances on
the same machine (ActiveMQ 5.12.1) with shared kahadb. During the process of setup, I have
setup different ports (61616 and 61626) for brokers.

However, when the second broker is started it would detect the lock on kahadb and goes into
"slave" mode with following log message.

----------------------------------------------------------------
INFO  | Database /opt/activemq/data/kahadb/lock is locked by another server. This broker is
now in slave mode waiting a lock to be acquired | org.apache.activemq.store.SharedFileLocker
| main
----------------------------------------------------------------

I have also noticed that none of the services are running on the ports configured for second
broker (for example, 61626). However, when the first broker is stopped/terminated then the
slave broker starts listening on configured ports and serves incoming requests.

Is this the expected behavior that in "slave" mode it will not run the services? If yes, I
am looking to run two brokers on same machine in master/slave mode to achieve "hot standby"
where client need to know about only one ActiveMQ connection URI (both application clients
and NoB configs). Is there anything I am missing here or potential gotchas?

Thanks


This e-mail transmission may contain information that is proprietary, privileged and/or confidential
and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention
or disclosure by any person other than the intended recipient or the intended recipient's
designees is strictly prohibited. If you are not the intended recipient or their designee,
please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds
may, at its sole discretion, monitor, review, retain and/or disclose the content of all email
communications.
Mime
View raw message