[
https://issues.apache.org/jira/browse/CAMEL-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sajjad Akhter updated CAMEL-8310:
---------------------------------
Description: Current implementation has requeue is set to false that means
there is no way for me to put back message in the queue if its one of the
downstream system is down (was: Current implementation is declaring both
exchange and queue on any init (producer or consumer). In case of producer one
don't need queue and may not know who going to be client.
We can add flag skipQueueDeclare so that it won't genrate uuid queue.
i can provide PR if it helps. )
> RabbitMQConsumer has hard coded requeue flag set to false
> ---------------------------------------------------------
>
> Key: CAMEL-8310
> URL: https://issues.apache.org/jira/browse/CAMEL-8310
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.14.1
> Reporter: Sajjad Akhter
> Fix For: 2.14.2
>
>
> Current implementation has requeue is set to false that means there is no way
> for me to put back message in the queue if its one of the downstream system
> is down
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
