Hello, I am using ActiveMQ 5.15.0 in a scenario where 300 producers are sending each every 5 seconds an event to one and the same queue. Since upgrading to 5.15.0 all duplicates which were detected by the audit process are forwarded to the DLQ, which is not wanted. This leads to the issue that alot of journal files of the kahadb are not cleaned because duplicates in DLQ are blocking the removal. According to the documentation this must not happen if a dead letter strategy is configured: *"The dead letter strategy has an message audit that is enabled by default. This prevents duplicate messages from being added to the configured DLQ"* ( source <http://activemq.apache.org/message-redelivery-and-dlq-handling.html> ) I found in the release notes of 5.15.0 a hint that this should be already fixed, but I cannot confirm: ticket <https://issues.apache.org/jira/browse/AMQ-6667> In my activemq.log I can find messages like: 2017-08-17 12:32:43,121 | WARN | org.apache.activemq.broker.region.cursors.QueueStorePrefetch@18e1ab6f:My.Queue,batchResetNeeded=false,size=0,cacheEnabled=true,maxBatchSize:1,hasSpace:true,pendingCachedIds.size:1,lastSyncCachedId:null,lastSyncCachedId-seq:null,lastAsyncCachedId:ID:09DC12000893-2955-636385757120625000-1:1:1:1:172,lastAsyncCachedId-seq:1626,store=permits:9999,sd=nextSeq:1629,lastRet:MessageOrderCursor:[def:0, low:0, high:0],pending:0 - cursor got duplicate send ID:09FC12000801-1834-636385719159843750-1:1:1:1:944 seq: org.apache.activemq.store.kahadb.KahaDBStore$StoreQueueTask$InnerFutureTask@3fffe287 | org.apache.activemq.broker.region.cursors.AbstractStoreCursor | ActiveMQ NIO Worker 5 2017-08-17 12:32:43,126 | WARN | duplicate message from store ID:09FC12000801-1834-636385719159843750-1:1:1:1:944, *redirecting for dlq processing* | org.apache.activemq.broker.region.Queue | ActiveMQ NIO Worker 5 Parts of activemq.xml: .........
Is this a bug or am I doing something wrong? -- View this message in context: http://activemq.2283324.n4.nabble.com/Duplicates-are-sent-to-DLQ-tp4729854.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
