the audit consists of a per producer bit map in a lru cache. the maxProducersToAudit determines the size of that lru cache.
if you will only ever have a single producer, then a maxProducersToAudit of 1 is sufficient. You may need to tune the value depending on the expected number of concurrent producers that the broker needs to deal with. In particular, the audit will suppress duplicate sends that may originate from a failover transport reconnect, so if you expect to have more than 64 concurrent producers that use failover, it would be advisable to increase the value. Having said that, the default kahadb store will suppress duplicate add attempts, provided the message has not already been dispatched (and removed from the index). So a working producer audit is a belt and braces approach to duplicate suppression. On 9 October 2012 12:16, jayeff <johannesfel...@googlemail.com> wrote: > Hi all, > > was does the attribute 'maxProducersToAudit' mean on a queue? I found no > description whatsoever on neither the ActiveMQ pages nor Google. > > Thanks & best regards, > Johannes Felten > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Description-of-queue-attribute-maxProducersToAudit-tp4657635.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
