[rabbitmq-discuss] redelivery after ACK

[Matthias Radestock]

Larry,

On 09/11/12 01:04, larry.edelstein at therealreal.com wrote:
> I'm asking questions and carefully reporting the behavior I've observed.

Indeed; you've done the right thing.

> I'm new to these tools - RabbitMQ server, and the ruby amqp gem. These
> tools have been around for a while, and the platforms I'm using -
> RabbitMQ and Ruby and Ubuntu, RabbitMQ and Ruby and Mac OS - are used by
> many, many developers. It would be -arrogant- and foolish of me to
> assume that I've immediately stumbled upon a bug in code that I expect
> has been well-exercised out there in the world. So I'm trying to
> determine if I'm traversing less-used code paths, using new features,
> implementing an unusual use case or pattern, misunderstanding how ACKs
> are supposed to work, or misunderstanding how client-side state is
> propagated.

There is nothing unusual about what you are trying to do and the tools 
you are using. And your understanding of acks appears correct.

Odds are that the behaviour you are seeing is due to some subtlety in 
the ruby amqp gem. I should think that the gem devs can get to the 
bottom of this very quickly.

Regards,

Matthias.