« Return to Thread: Failing to acquire exclusive lock - MySQL

Re: Failing to acquire exclusive lock - MySQL

by millea1 :: Rate this Message:

Reply to Author | View in Thread


James.Strachan wrote:
Which version of MySQL are you using? You are not running multiple
brokers against the same database are you by any chance?

I have this same problem when upgrading from 4.1 to 4.1.1 (mysql version 5.0.19) in a JBoss integration; the only broker running against the DB.



On 4/18/07, mjanveaux <mark@mobiledesigntech.com> wrote:
>
> Hello,
>
> I recently upgraded to ActiveMQ 4.1.1 from 4.0.1  I integrated ActiveMQ into
> my application using spring but not using the spring jms templates etc...
> Here's what I have in my spring configuration for my broker:
>
> <bean id="broker" class="org.apache.activemq.xbean.BrokerFactoryBean">
>     <property name="config"><value>/WEB-INF/activemq.xml</value></property>
>     <property name="start"><value>true</value></property>
> </bean>
>
> Here's my activemq.xml file...
> http://www.nabble.com/file/7936/activemq.xml activemq.xml
>
> My application is now failing to startup with the following messages in the
> logs over and over:
> INFO 17/04/2007 21:27:02 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Attempting to acquire
> the exclusive lock to become the Master broker
> DEBUG 17/04/2007 21:27:02 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Sleeping for 1000
> milli(s) before trying again to get the lock...
> INFO 17/04/2007 21:27:03 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Attempting to acquire
> the exclusive lock to become the Master broker
> DEBUG 17/04/2007 21:27:03 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Sleeping for 1000
> milli(s) before trying again to get the lock...
> INFO 17/04/2007 21:27:04 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Attempting to acquire
> the exclusive lock to become the Master broker
> DEBUG 17/04/2007 21:27:04 Main Thread
> org.apache.activemq.store.jdbc.DefaultDatabaseLocker - Sleeping for 1000
> milli(s) before trying again to get the lock...
>
>
> Am I missing a setting? Doing something wrong?  If anybody has some insight
> I'd appreciate this, I didn't have this problem before.
>
> Thank you
>
> Mark
> --
> View this message in context: http://www.nabble.com/Failing-to-acquire-exclusive-lock---MySQL-tf3598830s2354.html#a10051767
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


--

James
-------
http://radio.weblogs.com/0112098/

 « Return to Thread: Failing to acquire exclusive lock - MySQL