[
https://issues.apache.org/jira/browse/CAMEL-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417749#comment-15417749
]
ASF GitHub Bot commented on CAMEL-10239:
----------------------------------------
GitHub user gessnerfl opened a pull request:
https://github.com/apache/camel/pull/1116
CAMEL-10239: Provide implementation for publisher acknowledgement +
basic.return
This is a first implementation to support guaranteed delivery of mandatory
messages with rabbitmq. For more details please check the corresponding JIRA
ticket:
https://issues.apache.org/jira/browse/CAMEL-10239
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gessnerfl/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1116.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1116
----
commit 955ffb331a2c729ec8998e45b99c62ae6867b641
Author: Florian Gessner <[email protected]>
Date: 2016-08-11T18:54:48Z
CAMEL-10239: Provide implementation for publisher acknowledgement together
with basic.return
----
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
