[rabbitmq-discuss] Unacked messages going back in the queue
tim at rabbitmq.com
Fri Mar 22 11:24:47 GMT 2013
On 03/22/2013 10:54 AM, Tim Watson wrote:
> Hi Pierpaolo!
> On 03/22/2013 08:11 AM, Tim Watson wrote:
>> 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.
> Someone just kindly pointed out that you're using 3.0.4 - which means
> my advice isn't all that helpful as the server will negotiate
> heartbeats with the client by default (and pika has support for
> heartbeats). So my suspicion, is that if un-acked messages are
> disappearing and the client has not rejected them, that the connection
> must have been
> disrupted somehow (network failure, packet loss, ?) causing the broker
> to re-queue them, or the consumer must have crashed or a channel error
> generated. Is there anything in the logs to indicate what might be
In fact, depending on how you're interacting with the broker, that
heartbeat might not get handled by pika and the broker will disconnect
you anyway. Are you using BlockingConnection by any chance?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss