Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 871B7200B82 for ; Fri, 16 Sep 2016 14:30:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 85C0A160AD9; Fri, 16 Sep 2016 12:30:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C079A160A8C for ; Fri, 16 Sep 2016 14:30:22 +0200 (CEST) Received: (qmail 70661 invoked by uid 500); 16 Sep 2016 12:30:21 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 70642 invoked by uid 99); 16 Sep 2016 12:30:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Sep 2016 12:30:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B97C32C014F for ; Fri, 16 Sep 2016 12:30:21 +0000 (UTC) Date: Fri, 16 Sep 2016 12:30:21 +0000 (UTC) From: "Berge Stillingen (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-6424) Duplicate dead letter queues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 16 Sep 2016 12:30:23 -0000 [ https://issues.apache.org/jira/browse/AMQ-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496213#comment-15496213 ] Berge Stillingen commented on AMQ-6424: --------------------------------------- Note: A co-worker of mine experienced the same problem with version 5.13.0 - using default persistence configuration (Kahadb). > Duplicate dead letter queues > ---------------------------- > > Key: AMQ-6424 > URL: https://issues.apache.org/jira/browse/AMQ-6424 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, KahaDB > Affects Versions: 5.13.0, 5.13.3, 5.14.0 > Environment: JDK 1.8.0_93 , Windows Server 2012 R2 > Reporter: Berge Stillingen > Labels: database, journal, mssql, paging > > In version 5.14 (and 5.13.3) it appears the broker is able to 'occasionally' create extra DLQ-queues holding duplicate messages. > Browsing the admin console, you will sometimes see something like this: > - DLQ.myEventQueue > - DLQ.DLQ.myEventQueue > That both hold the samme message ID, eg. ID:ClientABC-61753-1471513949441-1:4:1:3:1 > The one from DLQ.myEventQueue is a standard entry caused by a client transaction rollback. > The (unwanted) one from DLQ.DLQ.myEventQueue has a > - dlqDeliveryFailureCause: java.lang.Throwable: duplicate paged in from store for queue://DLQ.myEventQueue > At some point you can even get a third queue named > - DLQ.DLQ.DLQ.myEventQueue holding another message with the samme MessageID and the same dlqDeliveryFailureCause > Reproduce: Haven't found a way to provoke the error. It happens occasionally in a semi-active test environment running with Mule 3.6.2. > Best guess is that there is some issue with the use of Journaling and synchronization between Kahadb and the MSSQL-database. > Configuration can be found at > http://activemq.2283324.n4.nabble.com/file/n4715868/activemq-anonymous.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)