[
https://issues.apache.org/jira/browse/CAMEL-15639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayyanar updated CAMEL-15639:
----------------------------
Attachment: RabbitMQ_Requeue_at_consumer_level.patch
> camel-rabbitmq - Add support for requeue at the Consumer level
> --------------------------------------------------------------
>
> Key: CAMEL-15639
> URL: https://issues.apache.org/jira/browse/CAMEL-15639
> Project: Camel
> Issue Type: New Feature
> Components: camel-rabbitmq
> Affects Versions: 3.4.4
> Reporter: Ayyanar
> Priority: Critical
> Fix For: 3.6.0
>
> Attachments: RabbitMQ_Requeue_at_consumer_level.patch
>
>
> _camel-rabbitmq - Add support for requeue at the Consumer level_
> Currently, in the rabbitmq while producing the record we need to set the
> below header to re-queu the data
> _rabbitmq.REQUEUE - To requue_
> *_Use case:_*
> From the other applicaiton or producer missed to add the above header,
> re-queue will not be happen if we failed to acknowledge. In this case,
> consumer can decide wheather the produced record can be requeue or not.
> However, above header will always have highest preference at the producer
> level. Since, the produced force fully says this data cannot be re-queue.
> Consumer property will not be considered. Consumer property will be consider
> only if this header is not available in the message body __
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
