Normally it is hard to see if two messages that are sent separately from each other are really the same. To implement this on the broker level might actually be a bit hard (imo)
However, there are a few ways you can work around this: 1) from the producer end: make sure that the producers do not produce the same data. For example such a thing can be prevented by placing the trigger on which the producers have to produce their messages on a queue; only one producer will consume this trigger and will produce the messages. 2) on the receiver / consumer end: build in logic to filter out doubles, or -even better- make sure the receiving end is idempotent; meaning that receiving the same data does not yield any problems. Both are viable, and might even for all kinds of reasons be combined. Not sure if this answers your question though. -- View this message in context: http://activemq.2283324.n4.nabble.com/High-availability-multiple-publishers-scenario-tp4720767p4720787.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
