configuration not working
Hi,
I am using master/slave configuration with AMQ 5.5.1.
The brokers are configured as master slave. Master has a lock on the db and
slaves waits to acquire the lock.
Application has queues configured using the failover protocol. e.g failover
tcp://:61616
PM
To: users@activemq.apache.org
Subject: RE: Master/slave configuration not working
Well,
this could be due to the locking mechanism which is implemented in Active MQ.
In MySQL I had simiilar problems, which could be solved switching the MySQL
engine to Inno DB.
--
View this message in context:
Well,
this could be due to the locking mechanism which is implemented in Active
MQ.
In MySQL I had simiilar problems, which could be solved switching the MySQL
engine
to Inno DB.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-slave-configuration-not-working
rom: Zagan [mailto:erbsen.fr...@gmail.com]
Sent: Wednesday, February 15, 2012 7:52 PM
To: users@activemq.apache.org
Subject: RE: Master/slave configuration not working
Which database do you use?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-slave-configuration-n
Which database do you use?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-slave-configuration-not-working-tp4390225p4390590.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
: Re: Master/slave configuration not working
Hi Chaitanya,
are you using Shared Database Master/Slave or Shared Filesystem Master/Slave?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-slave-configuration-not-working-tp4390225p4390422.html
Sent from the ActiveMQ
Hi Chaitanya,
are you using Shared Database Master/Slave or Shared Filesystem
Master/Slave?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Master-slave-configuration-not-working-tp4390225p4390422.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I am using master/slave configuration with AMQ 5.5.1.
The brokers are configured as master slave. Master has a lock on the db and
slaves waits to acquire the lock.
Application has queues configured using the failover protocol. e.g failover
tcp://:61616?wireFormat.maxInactivityDuration=0,tcp