The only codepath that can cause that exception is through the broker handling a 'basic. Ack', so this sounds like a client issue; check the client code.
The only codepath that can cause that exception is through the broker handling a 'basic. Ack', so this sounds like a client issue; check the client code. In particular, check that you aren't ack'ing messages more than once.
Doing so is in violation of the AMQP 0-9-1 spec: A message MUST not be acknowledged more than once. The receiving peer MUST validate that a non-zero delivery-tag refers to a delivered message, and raise a channel exception if this is not the case A great place to ask such questions is the rabbitmq-discuss mainling-list; all the RabbitMQ developers read that list and make a point of not leaving questions unanswered. It's also worth noting that previous versions of Rabbit were more lax and did not throw an error in this case, but more recent versions do.
I followed your advice and got an answer from Matthias from rabbitMQ - I will publish his answer here : I should have ack'ed messages . Therfore subscribe to a channel with ack=true --> channel. BasicConsume(queueName, true, queueingConsumer); .Thanks.
– user450602 Feb 27 at 15:26.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.