Hi Gary,
I set the logging level to DEBUG and after restarting, the log shows that
the select and update query for the ACTIVEMQ_LOCK times out. Here is the
exception:
2011-07-05 09:12:01,217 | INFO | Database lock driver override not found
for : [mysql-ab_
maybe try enabling trace level logging via log4j.properties and see if
there is anything more in the log.
You can reproduce this, right?
On 4 July 2011 17:01, farhad wrote:
> Hi Gary,
> Yes, I know, its very odd. But both jconsole and the log say that the broker
> is 'slave'!!?
> Regards, Farhad
Hi Gary,
Yes, I know, its very odd. But both jconsole and the log say that the broker
is 'slave'!!?
Regards, Farhad
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Fail-to-acquire-lock-Stays-as-slave-tp3643888p3643961.html
Sent from the ActiveMQ - User mailing list archive
That is very odd, if the lock acquire fails, the network adapters are
not started, so you should not be able to connect to the broker with a
jms client to send messages.
On 4 July 2011 16:31, farhad wrote:
> Hi,
> Sorry for the previous email. Here it is in a readable format:
> We've been running
Hi,
Sorry for the previous email. Here it is in a readable format:
We've been running activemq embedded brokers (5.4.2) with jboss 6.0 for a
while now without any problems. We've been using four brokers in a
master/slave configuration mixed with broker networks topoloy.
Now we are going to run acti
