Hello. We are running JDBC Master/Slave with ActiveMQ 5.2 and upon failing a master broker to slave broker we are seeing duplicate messages come through to the consumers processing a queue. These messages are not flagged as redelivered.
It's my understanding that the consumer is suppose to go through an audit routine to avoid duplicate deliveries but with multiple consumers on the same queue this does not seem to be the case. It seems as if the new master broker has no history of what the previous master broker send to consumers. So it could send a duplicate to consumer B while consumer A is still processing the same message, thus it's processed twice. Is this expected behavior during a broker failover from master to slave or should we not be getting duplicate messages? If so how does one handle this situation on the consumer end? -- View this message in context: http://www.nabble.com/duplicates-on-master-slave-broker-failover-tp25617860p25617860.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
