4
jchw
8y

Today I learned if you ack a message twice, RabbitMQ shits the bed. Dang. Another day wasted on a dumb refactoring regression.

Comments
  • 2
    I think that might just be your client. I did it by mistake once, and the message was received and acked, but client died, mq instance lived on tho
  • 0
    @nicholai yes, that's correct. It still gave rather odd behavior from my end. It seems it only aborted the connection if I double-acked a message that was sent immediate.
Add Comment