@Valantir007 Which transport are you using? Does the messenger:consume finish successfully?

Hi @weaverryan - I'm using Amqp. Yes, it does - the "messenger:consume" command has ended successfully but message is still with status "ready"... :/
Another thing I saw is that message is "unacknowledged" but after some time the message returns to "ready" but command is still working and processes the message.

When the message processing in the handler takes too long, it can be that rabbitmq regards it as failed and puts the message with a redelivered header back into the queue. You could check if that is the case.

That's right. Do you know how to fix that?

We took a look on this problem and we found issue with rabbitmq configuration on our server where rabbitmq is. I'm sorry for unnecessary task.

What was the issue?

Sorry for long time answers but I had to ask our administrator. We have RabbitMq with load balancing and our administrator added option:

backend rabbitmq_backend: option clitcpka
and
timeout client 3h

to configuration. Now everything works perfect. More in this post:

https://serverfault.com/questions/589804/haproxy-configuration-for-rabbitmq