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 wh
Thanks for this. I've managed to configure the database lease locker such
that the master will reclaim the lock if it is held by a slave. However,
I've encountered another issue while testing failover scenarios, that is, if
a slave yields the lock due to the master starting then the slave broker
sh
Hi,
I'm using a client to publish messages via the ActiveMQ REST API. I have a
single broker configured which is named *master-1*. Each time the broker
receives a message I get the following warning:
WARN | Broker localhost not started so using master-1 instead |
org.apache.activemq.broker.Broke
icks in.
>
> But for now, the question is what is keeping the java process alive?
>
>
>
> On 4 July 2013 17:51, hbakkum <
> hayden.bakkum@
> > wrote:
>> Thanks for this. I've managed to configure the database lease locker such
>> that the maste
Right, so I've tried to reproduce the issue again, but now the process does
indeed stop... perhaps I was imagining things :P
However it still does not restart as I'd like. But if I'm interpreting your
previous comment correctly I could achieve this by creating a custom Locker
which wraps and dele
Ok, I see. I'll take a look at those options, I think the simplest solution
will be to use something like Monit to just restart the process.
Appreciate your help on this.
Cheers,
Hayden.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Setting-a-Master-broker-in-a-Master
