[jira] [Commented] (CAMEL-13267) Camel stops consuming queue after restart of RabbitMQ broker

["Zoran Regvart (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779285#comment-16779285 ] 

Zoran Regvart commented on CAMEL-13267:
---------------------------------------

[~pbillen] have you noticed the {{automaticRecoveryEnabled}} endpoint property? Take look at the [component documentation|https://github.com/apache/camel/blob/master/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc] for other automatic recovery options.

> 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.
>  
> I am working on a self-contained example to demonstrate this issue. I will include this here later today.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)