[
https://issues.apache.org/jira/browse/CAMEL-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-9369.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.17.0
2.16.2
Thanks for reporting and the patch.
> Acknowledge messages for RabbitMQ InOut exchange when transferring exception
> ----------------------------------------------------------------------------
>
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.16.2, 2.17.0
>
> Attachments: CamelRabbitmqPatch.txt
>
>
> Currently if an exception is thrown during the processing of an InOut
> exchange on rabbitMQ, and both transferException=true and autoAck=false, the
> exception will be transferred back to the producer however the original
> message will remain unacknowledged. If the server is restarted, the
> application will attempt to reprocess the message.
> I would like to propose a patch to include a basicAck in the rabbitMQ
> consumer in this scenario. I’ve chosen to use a basicAck rather than a
> rejection given that the exception would be handled by the producer in this
> 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-exception-thrown-during-RabbitMQ-InOut-td5773786.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
