ion.commit(LocalTransaction.java:72)
... 13 more
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-backend-tp4341454p4669520.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Am 19.07.2013 00:49, schrieb slam:
Hi Christian,
In your multi master MySql setup, did you replicate the data? If not, will
you lose messages if one of the MySql servers that contains messages
failed/shut down?
assuming you did refer to me.
I do not run MySQL replication, like Master-Master
:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-backend-tp4341454p4669488.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Hi Christian,
In your multi master MySql setup, did you replicate the data? If not, will
you lose messages if one of the MySql servers that contains messages
failed/shut down?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster
slave after an exception (db failure), the vip is
>sending
>> traffic to the dead MQ as 61616 is still active!
>>
>> Good god! Its a nightmare. Can someone help? Has 5.8 resolved this issue?
>I
>> hope? Please someone advise.
>>
>>
>> thanks
>> Ali.
>>
>>
>>
>> --
>> View this message in context:
>http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-backend-tp4341454p4665253.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
node fails to cleanly close
> 61616/or become a slave after an exception (db failure), the vip is
sending
> traffic to the dead MQ as 61616 is still active!
>
> Good god! Its a nightmare. Can someone help? Has 5.8 resolved this issue?
I
> hope? Please someone advise.
>
>
>
db failure), the vip is sending
traffic to the dead MQ as 61616 is still active!
Good god! Its a nightmare. Can someone help? Has 5.8 resolved this issue? I
hope? Please someone advise.
thanks
Ali.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-
;
>
>
>
>
>
>
>
>
>--
>View this message in context:
>http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-backend-tp4341454p4665178.html
>Sent from the ActiveMQ - User mailing list archive at Nabble.com.
:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Master-slave-with-MySQLCluster-backend-tp4341454p4665178.html
Sent from the
That seems very reasonable.
The locker implementation can specified via configuration, it would be
great if you could provide an implementation that you can verify with
your setup.
note the interface:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/
Am 01.02.2012 17:57, schrieb Christian Hilgers:
Any Updates/comments here?
Am 31.01.2012 14:13, schrieb Gary Tully:
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lo
Am 31.01.2012 14:13, schrieb Gary Tully:
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lock impl (who's job it is to get an exclusive lock on the
store) treats failure
I had set up two brokers based on master-slave mode.
What I'm suffering are the two problems:
1, NDB store engine of Mysql cluster does not support distributed lock
so brokers based on master-slave mode fails to get the exclusive lock and
finally two masters are bringing up.
2, With the store
This need some work.
On 5.6, a single broker can deal with a failover of the jdbc store.
The difficulty is locking in the master/slave case, or peer cluster case.
The current lock impl (who's job it is to get an exclusive lock on the
store) treats failure of a lock as a fatal event and stops the b
Hi,
I am trying to setup a redundant ActiveMQ environment using
* ActiveMQ 5.5.1
* MySQL Cluster 5.1.47-ndb-7.1.5-cluster-gpl
* on Solaris 10 zones
* Java:
Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
Java HotSpot(TM) Server VM (build 20.2-b06, mixed mode)
* An application deployed i
15 matches
Mail list logo
