[
https://issues.apache.org/jira/browse/CAMEL-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779301#comment-16779301
]
Peter Billen edited comment on CAMEL-13267 at 2/27/19 1:19 PM:
---------------------------------------------------------------
[~zregvart] I added an example to the issue description. I will now look into
the auto-recovery option. Though, I believe the connection and consumer is
already being recovered, as all messages after the restart are into UNACKED
state. This means that have been delivered successfully to the consumer, but
not yet acknowledged.
Thanks for feedback! I will let you know if auto recovery helps here.
was (Author: pbillen):
[~zregvart] I added an example to the issue description. I will now look into
the auto-recovery option. Though, I believe the connection is already being
recovered, as all messages after the restart are into UNACKED state. This means
that have been delivered successfully to the consumer, but not yet acknowledged.
Thanks for feedback! I will let you know if auto recovery helps here.
> Camel stops consuming queue after restart of RabbitMQ broker
> ------------------------------------------------------------
>
> Key: CAMEL-13267
> URL: https://issues.apache.org/jira/browse/CAMEL-13267
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.23.0
> Reporter: Peter Billen
> Priority: Major
>
> I am consuming a RabbitMQ queue as following:
>
> {code:java}
> from("rabbitmq://localhost:5672?username=test&password=test&declare=false&queue=q&autoAck=false&threadPoolSize=1&exclusiveConsumer=true")
> .to("log:receive");{code}
>
> When I restart the RabbitMQ broker, no messages are longer received in the
> log handler.
>
> According the management interface, all pending messages are in UNACKED
> state. This means that they are transmitted to the consumer, but not
> acknowledged. In other words, Camel was able to restore the connection after
> the restart, but fails to deliver to the log handler and acknowledge them
> afterwards.
>
> I did not test this, but I believe the consumer will eventually crash due to
> OOM.
>
> **example**
>
> Please find a self-contained example on
> [https://github.com/pbillen/playground-camel-13267.] You need a (local)
> Docker daemon to run this. Use it as following:
>
> # Start with `mvn clean install -U`.
> # You notice in the logging that every 500ms, a message is sent and
> received. You can also log into the administrator interface on
> [http://localhost:15672|http://localhost:15672/] with login/password `test`.
> You will see the message pass through every 500ms. Great!
> # Now restart the RabbitMQ broker. Typically, find the container identifier
> with `docker ps` and then execute `docker restart <identifier>`.
> # After restart, you notice that every 500ms a message is sent, but not
> received. You can also log into the administrator interface and see that all
> messages are into the UNACKED state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
