Due to https://issues.apache.org/jira/browse/AMQ-5016 our large and stable systems will hit the 2^31 + 1 message limit after a few days. I gather that the "checkForDuplicates" flag will prevent the "Duplicate dispatch on connection" issue. I can set that flag on just our highest volume queues but that just delays the problem a bit (when a lower volume queue hits the same limit), I would like to set that flag system wide but would like to know more about what I am disabling.
I haven't been able to find a lot of documentation on this flag. What are the risks of disabling duplicate checking system wide? Are there any cases where this flag must stay enabled? Our usage of activemq is pretty basic, all AUTO_ACK and no transactions so I am guessing we should be safe but I can't be sure. We do use failover:tcp: connector but only for the reconnecting, we only have a single broker. Sam
