You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/08/12 06:59:20 UTC

[jira] [Resolved] (CAMEL-10239) Extend Camel RabbitMQ with guaranteed delivery (basic.return)

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

Claus Ibsen resolved CAMEL-10239.
---------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s: 2.18.0

Thanks for the PR

> 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
>            Assignee: Claus Ibsen
>              Labels: camel, github-pullrequest, newbie, patch, rabbitmq
>             Fix For: 2.18.0
>
>
> 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)