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 82585200D24 for ; Tue, 24 Oct 2017 15:41:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 810BC160BF1; Tue, 24 Oct 2017 13:41:06 +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 C5DBB160BDB for ; Tue, 24 Oct 2017 15:41:05 +0200 (CEST) Received: (qmail 53408 invoked by uid 500); 24 Oct 2017 13:41:05 -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 53399 invoked by uid 99); 24 Oct 2017 13:41:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2017 13:41:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 396271A14BE for ; Tue, 24 Oct 2017 13:41:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id IiFjL5dgRpVx for ; Tue, 24 Oct 2017 13:41:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 30BB460E01 for ; Tue, 24 Oct 2017 13:41:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E6DDBE0F17 for ; Tue, 24 Oct 2017 13:41:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4DAA5212FF for ; Tue, 24 Oct 2017 13:41:00 +0000 (UTC) Date: Tue, 24 Oct 2017 13:41:00 +0000 (UTC) From: "Alvin Kwekel (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-6847) Immediate poison ACK after move from DLQ leads to message loss MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 Oct 2017 13:41:06 -0000 [ https://issues.apache.org/jira/browse/AMQ-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alvin Kwekel updated AMQ-6847: ------------------------------ Description: *Setup* * setMaximumRedeliveries(0) * Throw RuntimeException (Poison ACK) in consumer directly after receiving message *Scenario* * Move message from DLQ to original input queue (either web console or JMX retryMessages) * Processing of message fails again directly * The message is considered to be still on the DLQ on the rejection and ActiveMQ logs "Not adding duplicate to DLQ" Introducing a delay before throwing the exception in the client will get around the issue. I initially noticed the issue when using an AMQP reject (Apache Qpid Proton) after which I reproduced similar conditions (instant poison ACK) it with the JMS client. The attached Java app will reproduce the issue on 5.14.5 and 5.15.2. Might be related to AMQ-5752. 2017-10-24 13:38:11,275 | DEBUG | Not adding duplicate to DLQ: ID:xxx-32848-1508845049112-6:1:1:1:1, dest: queue://TEST | org.apache.activemq.broker.region.policy.AbstractDeadLetterStrategy | ActiveMQ Transport: tcp:///127.0.0.1:36360@61616 was: *Setup* * setMaximumRedeliveries(0) * Throw RuntimeException (Poison ACK) in consumer directly after receiving message *Scenario* * Move message from DLQ to original input queue * Processing of message fails again directly * The message is considered to be still on the DLQ on the rejection and ActiveMQ logs "Not adding duplicate to DLQ" Introducing a delay before throwing the exception in the client will get around the issue. I initially noticed the issue when using an AMQP reject (Apache Qpid Proton) after which I reproduced similar conditions (instant poison ACK) it with the JMS client. The attached Java app will reproduce the issue on 5.14.5 and 5.15.2. Might be related to AMQ-5752. 2017-10-24 13:38:11,275 | DEBUG | Not adding duplicate to DLQ: ID:xxx-32848-1508845049112-6:1:1:1:1, dest: queue://TEST | org.apache.activemq.broker.region.policy.AbstractDeadLetterStrategy | ActiveMQ Transport: tcp:///127.0.0.1:36360@61616 > Immediate poison ACK after move from DLQ leads to message loss > -------------------------------------------------------------- > > Key: AMQ-6847 > URL: https://issues.apache.org/jira/browse/AMQ-6847 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 5.14.5, 5.15.2 > Reporter: Alvin Kwekel > Attachments: FailingReceiver.java, dlq-redelivery-issue.tar.gz > > > *Setup* > * setMaximumRedeliveries(0) > * Throw RuntimeException (Poison ACK) in consumer directly after receiving message > *Scenario* > * Move message from DLQ to original input queue (either web console or JMX retryMessages) > * Processing of message fails again directly > * The message is considered to be still on the DLQ on the rejection and ActiveMQ logs "Not adding duplicate to DLQ" > Introducing a delay before throwing the exception in the client will get around the issue. > I initially noticed the issue when using an AMQP reject (Apache Qpid Proton) after which I reproduced similar conditions (instant poison ACK) it with the JMS client. The attached Java app will reproduce the issue on 5.14.5 and 5.15.2. > Might be related to AMQ-5752. > > 2017-10-24 13:38:11,275 | DEBUG | Not adding duplicate to DLQ: ID:xxx-32848-1508845049112-6:1:1:1:1, dest: queue://TEST | org.apache.activemq.broker.region.policy.AbstractDeadLetterStrategy | ActiveMQ Transport: tcp:///127.0.0.1:36360@61616 -- This message was sent by Atlassian JIRA (v6.4.14#64029)