[
https://issues.apache.org/jira/browse/CAMEL-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-12746:
-----------------------------------
Assignee: Claus Ibsen
> Temporary reply queues being created with main endpoint autoAck setting
> -----------------------------------------------------------------------
>
> Key: CAMEL-12746
> URL: https://issues.apache.org/jira/browse/CAMEL-12746
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.20.2
> Reporter: Valdis
> Assignee: Claus Ibsen
> Priority: Major
> Labels: rabbitmq
> Fix For: 2.21.3, 2.22.1, 2.23.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> As discussed here:
> [http://camel.465427.n5.nabble.com/Camel-with-Rabbitmq-messages-in-temp-reply-queue-not-being-acked-td5822286.html]
> When temporary reply queues are used on InOut capable routes with autoAck set
> to false on the main queue(s) the reply messages keep piling up in the
> temporary queue in an un-acked state until a consumer restart.
> This can be prevented with a change to the TemporaryQueueReplyManager line
> 139 to always start the consumer of temprary queues with auto acknowledge
> mode of true.
> Changing this:
> private void start() throws IOException {
> tag = channel.basicConsume(getReplyTo(), endpoint.isAutoAck(), this);
> }
> To:
> private void start() throws IOException {
> tag = channel.basicConsume(getReplyTo(), *true*, this);
> }
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
