Thanks for the reply.  We've tested both settings and we have the following
concerns.  We would like to have a HA setting using master/slave and we want
to find out how to setup HA mysql database correctly.  Please advise.

1) For Federated network of brokers, only one broker will persist messages
when a client is connected to it.  We tested the forward and replay
scenarios and everything works fine.  The only concern is this approach is
not HA because the messages will not be available while the broker is
unavaliable.    According to the documentation on the Activemq site, this
approach is not HA.

2) For master/slave setting, ActiveMQ will not be HA if the shared mysql
database is down.  So, we are trying to setup a master/slave mysql database
environment and connect ActiveMQ similar to Christian's post listed above. 
We've configured mysql database to replicate from master to slave to
guarantee no messages will be lost if mysql master is offline.  However, we
encountered database exceptions when consumers sending acknowledgements to
the broker if we failover from one broker to another.

Caused by: java.io.IOException: Duplicate entry '241' for key 'PRIMARY'
        at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:45)
        at
org.apache.activemq.store.jdbc.TransactionContext.commit(TransactionContext.java:178)
        at
org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.commitTransaction(JDBCPersistenceAdapter.java:497)
        at
org.apache.activemq.store.memory.MemoryTransactionStore$Tx.commit(MemoryTransactionStore.java:110)
        at
org.apache.activemq.store.memory.MemoryTransactionStore.commit(MemoryTransactionStore.java:259)
        at
org.apache.activemq.transaction.LocalTransaction.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.

Reply via email to