To totally eliminate dlq processing, specify a null or empty strategy <deadLetterStrategy/> On Nov 20, 2012 9:18 a.m., "jayeff" <johannesfel...@googlemail.com> wrote:
> Hi all, > > I'm facing the following problem, maybe someone can help with this as I > couldn't find helpful suggestions when searching the mailinglist or Google. > > I have an application running an embedded broker with three queue, no > topics. Messages are put into the queues inside a transaction with 1-30 > messages per transaction. Persistance is through kahadb. I don't want any > messages to be redelivered but discarded instead, so I used the below > snippet in the activemq.xml as suggested at > http://activemq.apache.org/message-redelivery-and-dlq-handling.html > <http://activemq.apache.org/message-redelivery-and-dlq-handling.html> : > > ... > <policyEntry queue=">" producerFlowControl="true" memoryLimit="2gb" > enableAudit="false" maxPageSize="100" > > > <deadLetterStrategy> > <sharedDeadLetterStrategy processExpired="false" /> > </deadLetterStrategy> > > > <pendingQueuePolicy> > <fileQueueCursor /> > </pendingQueuePolicy> > </policyEntry> > ... > > I was under the impression that this would discard e.g. all expired > messages. However looking at the broker with jvisualvm I see a 4th queue > called ActiveMQ.DLQ which seems to be the default dlq. > > Am I missing out on something? > > Best regards, > Johannes > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-DLQ-appears-even-though-sharedDeadLetterStrategy-processExpired-false-tp4659556.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
