[rabbitmq-discuss] Messages unexpectedly moving from Unacked to Ready

[Simon MacMullen]

On 30/01/14 17:10, Patrick Long wrote:
> The only way I could see it happen was if one of the other processing
> threads looking at the _*same *_queue called close. However they do not
> share channels and I assume that closing on a channel different to the
> one that retrieved the message would not effect the Unacked state, correct?

That's correct. Closing a channel releases all the unacked messages on 
that channel...

On 30/01/14 17:12, Patrick Long wrote:
> Ah so that makes it sound like the connection does not need to be
> closed by the specific channel for that to happen

...and closing a connection implicitly closes all the channels on that 
connection, releasing all their unacked messages.

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, Pivotal