Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 11 Aug 2016 19:01:20 +0000 (UTC)
From: "Florian Gessner (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12996724.1470941638000.285762.1470942080502@Atlassian.JIRA>
In-Reply-To: <JIRA.12996724.1470941638000@Atlassian.JIRA>
References: <JIRA.12996724.1470941638000@Atlassian.JIRA> <JIRA.12996724.1470941638272@arcas>
Subject: [jira] [Updated] (CAMEL-10239) Extend Camel RabbitMQ with
 guaranteed delivery (basic.return)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 Aug 2016 19:01:22 -0000


     [ https://issues.apache.org/jira/browse/CAMEL-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Gessner updated CAMEL-10239:
------------------------------------
    Description: 
So far camel-rabbitmq supports publisher acknowledgements to ensure that a massage was delivered to the brokers. However this does not guarantee that the message is delivered to queue (https://www.rabbitmq.com/confirms.html - 'When will messages be confirmed?').

To implement guaranteed delivery publisher acknowledgements have to be activated together with a *return listener* and publishing messages as mandatory.
In this case the basic.return will be returned to the publisher before the basic.nack or basic.ack. Only in this case we can be sure that the message is really delivered to the configured queue (or fails if no queue is available).

As a solution I provided a pull request on github together with integration tests.

https://github.com/apache/camel/pull/1116

Please let me know if I can provide further support/input.

  was:
So far camel-rabbitmq supports publisher acknowledgements to ensure that a massage was delivered to the brokers. However this does not guarantee that the message is delivered to queue (https://www.rabbitmq.com/confirms.html - 'When will messages be confirmed?').

To implement guaranteed delivery publisher acknowledgements have to be activated together with a *return listener* and publishing messages as mandatory.
In this case the basic.return will be returned to the publisher before the basic.nack or basic.ack. Only in this case we can be sure that the message is really delivered to the configured queue (or fails if no queue is available).

As a solution I provided a pull request on github together with integration tests.


> Extend Camel RabbitMQ with guaranteed delivery (basic.return)
> -------------------------------------------------------------
>
>                 Key: CAMEL-10239
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10239
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-rabbitmq
>    Affects Versions: 2.17.2
>            Reporter: Florian Gessner
>              Labels: camel, github-pullrequest, newbie, patch, rabbitmq
>
> So far camel-rabbitmq supports publisher acknowledgements to ensure that a massage was delivered to the brokers. However this does not guarantee that the message is delivered to queue (https://www.rabbitmq.com/confirms.html - 'When will messages be confirmed?').
> To implement guaranteed delivery publisher acknowledgements have to be activated together with a *return listener* and publishing messages as mandatory.
> In this case the basic.return will be returned to the publisher before the basic.nack or basic.ack. Only in this case we can be sure that the message is really delivered to the configured queue (or fails if no queue is available).
> As a solution I provided a pull request on github together with integration tests.
> https://github.com/apache/camel/pull/1116
> Please let me know if I can provide further support/input.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)