[rabbitmq-discuss] Unacked messages going back in the queue
watson.timothy at gmail.com
Fri Mar 22 08:11:00 GMT 2013
If the channel is disappearing (because rabbit considers the connection to have dropped) then I would suggest configuring heartbeats in your client too ensure the connection stays alive.
On 22 Mar 2013, at 03:36, Pierpaolo Baccichet <pierpaolo at dropbox.com> wrote:
> Hello everybody,
> I am using rabbitMQ 3.0.4 clustered and a replicated queue in memory. I connect one consumer (using pika) in acked mode. The worker fetches the message and processes it for very long time directly on the pika thread.
> After some time, I see the message going back in ready state and the consumer disappear from the queue in the rabbit console. I am assuming this is due to the consumer not sending some kind of keepalive message back to rabbit to maintain the channel in healthy state.
> Is there anything I can do to change the TTL?
> Best, Pierpaolo
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss