Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 365BB185CC for ; Tue, 13 Oct 2015 13:05:32 +0000 (UTC) Received: (qmail 71417 invoked by uid 500); 13 Oct 2015 13:05:15 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 71375 invoked by uid 500); 13 Oct 2015 13:05:15 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 71363 invoked by uid 99); 13 Oct 2015 13:05:14 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2015 13:05:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 69C9EC39D6 for ; Tue, 13 Oct 2015 13:05:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.565 X-Spam-Level: **** X-Spam-Status: No, score=4.565 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 0SViyMke_RSl for ; Tue, 13 Oct 2015 13:05:09 +0000 (UTC) Received: from mail-io0-f173.google.com (mail-io0-f173.google.com [209.85.223.173]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id BF71320B57 for ; Tue, 13 Oct 2015 13:05:08 +0000 (UTC) Received: by iow1 with SMTP id 1so19916330iow.1 for ; Tue, 13 Oct 2015 06:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=CYE/nsyTnQQf3H6u5DVHyBnauvc9fXivHDBSvlbYu+M=; b=K+ThqMCCKZ7J0WTyZsYEryTDQMvS9ydepYd8TWT+U4jbXICa9rJIfE+2ncUmlIBkFn rvilDX4gQTfxU5V5piAcGlCcrcA6XdmYPSabr7ZBUaDKKR7tAqbEfoBy3z/Kdnx+UD6b oSVHM6vWUro4uNuToEj0fbjvZPzH0PjZOLUCw+/ex+hSbn4gB6bKxdxPs8H3+vlA1WMM eY7LotXswoAG6tMFPfQO6U4Uu0YPNDP8XqD5NlStWkBucNtPmMVQ/Md98iqQvDXJ7D17 cocPLmin36JOHYm4Od2RxZqN5Y7mDyLdzcsIgplQuKIeIhBqDHG5tfhQehTLi8qHHHfd dWOA== MIME-Version: 1.0 X-Received: by 10.107.47.32 with SMTP id j32mr33528728ioo.76.1444741507795; Tue, 13 Oct 2015 06:05:07 -0700 (PDT) Sender: tbain98@gmail.com Received: by 10.50.78.227 with HTTP; Tue, 13 Oct 2015 06:05:07 -0700 (PDT) Received: by 10.50.78.227 with HTTP; Tue, 13 Oct 2015 06:05:07 -0700 (PDT) In-Reply-To: <1444380974302-4702800.post@n4.nabble.com> References: <1444380974302-4702800.post@n4.nabble.com> Date: Tue, 13 Oct 2015 07:05:07 -0600 X-Google-Sender-Auth: hYuj9DrjqlLXb80Vz7i8SPq2fcA Message-ID: Subject: Re: Message disappears after JMX-retry on DLQ when processing fails for a second time From: Tim Bain To: ActiveMQ Users Content-Type: multipart/alternative; boundary=001a11c14caa5d54630521fc1805 --001a11c14caa5d54630521fc1805 Content-Type: text/plain; charset=UTF-8 Boris, That's an old enough bug that I think we're better off creating a new bug in JIRA and simply linking the two together. Can you please submit it, along with any configuration or procedures you needed to reproduce the problem reliably? Tim On Oct 9, 2015 8:15 AM, "boriss" wrote: > I'm using the latest AMQ-5.12.0, trying to recover messages which failed > enough times to be moved to the DLQ. Invoking the retryMessage(messageId) > and retryMessages() operations from JMX results that if the consumer fails > again to consume, the message disappears completely and is being lost. > > I saw this JIRA (https://issues.apache.org/jira/browse/AMQ-3405) which > basically describes this misfunctionality. It looks like that this bug can > be reopened. > > Thanks, best Regards, > Boris > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-disappears-after-JMX-retry-on-DLQ-when-processing-fails-for-a-second-time-tp4702800.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > --001a11c14caa5d54630521fc1805--