Queues are getting deleted in RabbitMQ

[HasanMdArik]

So I created some queues with the command below...

rabbitmqadmin --username=<username> --password=<password> --vhost=blocking-mq declare queue name="data-api-queue" durable=true auto_delete=false 'arguments={"x-message-ttl":1200000,"x-expires":1200000}'
rabbitmqadmin --username=<username> --password=<password> --vhost=blocking-mq declare queue name="interaction-api-queue" durable=true auto_delete=false 'arguments={"x-message-ttl":1200000,"x-expires":1200000}'
rabbitmqadmin --username=<username> --password=<password> --vhost=blocking-mq declare queue name="realtime-api-queue" durable=true auto_delete=false 'arguments={"x-message-ttl":1200000,"x-expires":1200000}'
rabbitmqadmin --username=<username> --password=<password> --vhost=blocking-mq declare queue name="blocking-api-queue" durable=true auto_delete=false 'arguments={"x-message-ttl":1200000,"x-expires":1200000}'

But after restarting my machine I see that they are deleted. I created them again and restarted and that occurred again. But exchange declared in a same-ish manner(with rabbitmqadmin) persisted and also queues of the other vhost are still there too...

N.B. The persisting queues of the other vhost was created via the management panel.

How to solve this issue(without declaring queues after every reboot)...???

EDIT: Also, sudo systemctl restart rabbitmq-server.service doestn't delete the queues...

[michaelklishin]

Your queues have TTL defined for them and messages in them. Durable queues with TTL generally make no sense. Please review what extra arguments you use and why.

If you want to track deletion events, see internal events. It should be easy to spot that they happen roughly around the time TTL kicks in after last consumer disconnection.

[HasanMdArik]

So are TTLs the reason queues are getting deleted?

One the second paragraph, I don't see such logs..

{"event":"channel.closed","user_who_performed_action":"blocking-api","pid":"<[email protected]>","timestamp_in_ms":1671710832393}
{"event":"consumer.deleted","user_who_performed_action":"rmq-internal","queue":"blocking-api-queue","vhost":"blocking-mq","channel":"<[email protected]>","consumer_tag":"ctag-/tmp/go-build3081336456/b001/exe/blocking-api-1","timestamp_in_ms":1671710832393}
{"event":"channel.closed","user_who_performed_action":"blocking-api","pid":"<[email protected]>","timestamp_in_ms":1671710832393}
{"event":"channel.closed","user_who_performed_action":"blocking-api","pid":"<[email protected]>","timestamp_in_ms":1671710832393}
{"event":"connection.closed","client_properties":["{<<\"product\">>,longstr,<<\"https://github.com/streadway/amqp\">>}","{<<\"version\">>,longstr,<<\"β\">>}","{<<\"capabilities\">>,table,[{<<\"consumer_cancel_notify\">>,bool,true},{<<\"connection.blocked\">>,bool,true}]}"],"node":"rabbit@linux-machine","pid":"<[email protected]>","name":"192.168.1.105:48656 -> 192.168.1.105:5672","timestamp_in_ms":1671710832397}
{"event":"node.node.stats","send_bytes":14597,"recv_bytes":681,"sock_port":25672,"sock_addr":"192.168.1.105","peer_port":58276,"peer_addr":"192.168.1.105","route":"{'rabbit@linux-machine','rabbitmqcli-686-rabbit@linux-machine'}","timestamp_in_ms":1671710835229}
{"event":"node.node.stats","send_bytes":14877,"recv_bytes":681,"sock_port":25672,"sock_addr":"192.168.1.105","peer_port":58276,"peer_addr":"192.168.1.105","route":"{'rabbit@linux-machine','rabbitmqcli-686-rabbit@linux-machine'}","timestamp_in_ms":1671710840232}
{"event":"node.node.stats","send_bytes":15157,"recv_bytes":681,"sock_port":25672,"sock_addr":"192.168.1.105","peer_port":58276,"peer_addr":"192.168.1.105","route":"{'rabbit@linux-machine','rabbitmqcli-686-rabbit@linux-machine'}","timestamp_in_ms":1671710845235}
{"event":"node.node.stats","send_bytes":15437,"recv_bytes":685,"sock_port":25672,"sock_addr":"192.168.1.105","peer_port":58276,"peer_addr":"192.168.1.105","route":"{'rabbit@linux-machine','rabbitmqcli-686-rabbit@linux-machine'}","timestamp_in_ms":1671710850237}

Here is the log after clients disconnected, no queue deletion...

EDIT: Also, sudo systemctl restart rabbitmq-server.service doestn't delete the queues...

[HasanMdArik]

I get it, message TTL is not the issue but the x-expires argument deletes the queue...