[rabbitmq-discuss] Losing messages, why?

[DOBRO Sergei]

Matthias,

I can confirm that the issue is not resolved yet.
Those queues which have messages_ready are not relevant to the case because all of them are bound to the other (fanout) exchange. Each worker's queue is bound to another direct exchange with its own routing key.

I've noticed that the issue occurs chiefly when the worker's queue is in heavy load state.

But when the workers stop receving messages, none of their queues have messages_ready or messages_unacknowledged.
Here is the output I've saved when it happened last time.

# rabbitmqctl list_queues name messages messages_ready messages_unacknowledged |grep daemon
daemon-8698-1298682602  0       0       0
daemon-8711-1298682602  0       0       0
daemon-8700-1298682602  0       0       0
daemon-8699-1298682602  0       0       0
daemon-8704-1298682602  0       0       0
daemon-8710-1298682602  0       0       0
daemon-8706-1298682602  0       0       0
daemon-8702-1298682602  0       0       0
daemon-8701-1298682602  0       0       0
daemon-8707-1298682602  0       0       0

The full output of rabbitmqctl list_{exchanges,queues,bindings,consumers,connections,channels} I have published here:
http://old.nabble.com/Losing-messages%2C-why--td30958766.html

BTW, workers are Perl (Net::RabbitMQ) clients. Does it matter?

Thanks a lot for your support!

DOBRO.

28.02.2011, 18:13, "Matthias Radestock" <matthias at rabbitmq.com>:
> On 26/02/11 10:32, DOBRO wrote:
>
>>  Now I understand why messages_ready in some queues grow up in time.
>>  That's because of connection was closed not properly.
>>
>>  Actually, these queues disappear later.
>
> So is there still a problem? Has the original "some workers stop
> receiving messages from some queues" issue been resolved?
>
> Matthias.