Hi i am using activemq 5.6.0 on amazon EC2, i used activemq jdbc master slave High-availability configuration, aws rds mysql server is the persistence store.
aws rds supports auto-failover, if one mysql is died, it will auto-failover to another mysql in few minutes. when failover happens, master activemq server will lost db-lock, slave activemq server gets the db lock and becomes the master when failover is finished. i found lots of message insertion failure after failover, the error will disappear once messageIdGenerator passed duplicated Id range. Any idea how it could happen? thanks eric WARN | Error while closing connection: Duplicate entry '42460789' for key 'PRIMARY' INFO | jvm 3 | 2012/09/02 06:52:49 | java.sql.BatchUpdateException: Duplicate entry '42460789' for key 'PRIMARY' INFO | jvm 3 | 2012/09/02 06:52:49 | at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2024) INFO | jvm 3 | 2012/09/02 06:52:49 | at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1449) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:103) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.jdbc.TransactionContext.executeBatch(TransactionContext.java:81) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.jdbc.TransactionContext.close(TransactionContext.java:129) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.jdbc.JDBCMessageStore.addMessage(JDBCMessageStore.java:129) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.memory.MemoryTransactionStore.addMessage(MemoryTransactionStore.java:307) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.store.memory.MemoryTransactionStore$1.asyncAddQueueMessage(MemoryTransactionStore.java:150) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:734) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.region.Queue.send(Queue.java:707) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:407) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:503) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:305) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:129) INFO | jvm 3 | 2012/09/02 06:52:49 | at org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:96) -- View this message in context: http://activemq.2283324.n4.nabble.com/Error-while-closing-connection-Duplicate-entry-for-key-PRIMARY-tp4656164.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
