Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 52F071899C for ; Fri, 27 Nov 2015 04:47:11 +0000 (UTC) Received: (qmail 9480 invoked by uid 500); 27 Nov 2015 04:47:11 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 9437 invoked by uid 500); 27 Nov 2015 04:47:11 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 9425 invoked by uid 99); 27 Nov 2015 04:47:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Nov 2015 04:47:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E49A92C044E for ; Fri, 27 Nov 2015 04:47:10 +0000 (UTC) Date: Fri, 27 Nov 2015 04:47:10 +0000 (UTC) From: "E Wong (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-9369) Acknowledge messages for RabbitMQ InOut exchange when transferring exception MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-9369?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] E Wong updated CAMEL-9369: -------------------------- Flags: (was: Patch) > Acknowledge messages for RabbitMQ InOut exchange when transferring except= ion > -------------------------------------------------------------------------= --- > > Key: CAMEL-9369 > URL: https://issues.apache.org/jira/browse/CAMEL-9369 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq > Affects Versions: 2.16.1 > Reporter: E Wong > Priority: Minor > Attachments: CamelRabbitmqPatch.txt > > > Currently if an exception is thrown during the processing of an InOut exc= hange on rabbitMQ, and both transferException=3Dtrue and autoAck=3Dfalse, t= he exception will be transferred back to the producer however the original = message will remain unacknowledged. If the server is restarted, the applic= ation will attempt to reprocess the message. > I would like to propose a patch to include a basicAck in the rabbitMQ con= sumer in this scenario. I=E2=80=99ve chosen to use a basicAck rather than = a rejection given that the exception would be handled by the producer in th= is scenario and there should be no need to deadletter/requeue the messages = on rabbitmq. > More details on our setup here: > http://camel.465427.n5.nabble.com/Messages-remain-unacknowledged-when-exc= eption-thrown-during-RabbitMQ-InOut-td5773786.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)