activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: Setting a Master broker in a MasterSlave configuration
Date Wed, 03 Jul 2013 14:43:07 GMT
There isn't any eviction strategy or preferred master election strategy for
the current lock implementations. They effectively compete around some
shared mutex and first one to win is elected master. The lock
implementations are pluggable, however, so you can take a look

Take a look here

On Tue, Jul 2, 2013 at 6:36 PM, hbakkum <> wrote:

> Hi,
> I have set up ActiveMQ in a JDBC MasterSlave configuration. I have a use
> case where it would be useful to mark a broker as the "Master" broker which
> would always take a lock if it was owned by a slave. Is there anyway of
> doing this or something similar, e.g. some sort of order of precedence when
> brokers compete for the lock?
> I would be able to achieve this perhaps by restarting the slaves when the
> "Master" is available but does not hold the lock, however it would be much
> cleaner if I could just configure a master broker which always takes the
> lock.
> Any help would be most appreciated.
> Thanks,
> Hayden.
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

*Christian Posta*
twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message