[ 
https://issues.apache.org/jira/browse/CAMEL-9399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046785#comment-15046785
 ] 

ASF GitHub Bot commented on CAMEL-9399:
---------------------------------------

GitHub user FingolfinTEK opened a pull request:

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

    Implementation of CAMEL-9399

    Added support for RabbitMQ Publisher Acknowledgements, did a little code 
cleanup, added two producer integration tests that test out publisher 
acknowledgements.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/FingolfinTEK/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/717.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 #717
    
----
commit 93bede4db144913ce8c1cfe07aa17ed16ea5acbe
Author: Miloš Milivojević <[email protected]>
Date:   2015-12-08T11:15:55Z

    CAMEL-9399 Implementation and integration tests

commit ea8b2f4cafd1d4d87193ad4c98bba00311acf088
Author: Miloš Milivojević <[email protected]>
Date:   2015-12-08T11:45:02Z

    Merge branch 'master' of https://github.com/apache/camel

----


> Provide support for Publisher Acknowledges
> ------------------------------------------
>
>                 Key: CAMEL-9399
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9399
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-rabbitmq
>            Reporter: Miloš Milivojević
>            Priority: Minor
>
> Currently, when publishing a message through Camel there is no way make sure 
> that the message was actually delivered to appropriate queues which does not 
> meet the reliability requirements of certain mission-critical applications. 
> While there are two ways of doing this - AMQP transactions and RabbitMQ's 
> Confirms - the former is considered overly heavyweight and latter is 
> preferred [as per RabbitMQ's 
> documentation|https://www.rabbitmq.com/confirms.html].
> New configuration properties should be added to RabbitMQ endpoint - a boolean 
> property for enabling publisher acknowledges and a long property for 
> configuring a timeout (in most cases the publisher will not want to wait 
> forever for a confirmation).
> I am almost done with the implementation - the only thing left to do is to 
> perform a bit of code cleanup and add a few integration tests to verify that 
> the acknowledges are working correctly.



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

Reply via email to