Queue Declare error with amq prefix

[ray zuniga]

RMQ v3.10.7 erlan 25.0.4

Client version: py-amqp 5.1.1

Error:

+++++

AMQP Access Refused 403 queue.declare : queue name 'amq.xx' contains reserved amq prefix

++++++

I have an app team that is getting the above error and im trying to figure out if its something in their reconnect logic that is causing this error specifically plus improper re-use of the auto generated name.

After reading this section of the docs

https://www.rabbitmq.com/queues.html#server-named-queues

my theory sounds about right but I cant properly convey to them that this inst a broker side issue.

Any thoughts? tips ?

[David Ansari]

Please read https://www.rabbitmq.com/queues.html#names

> Queue names starting with "amq." are reserved for internal use by the broker. Attempts to declare a queue with a name that violates this rule will result in a channel-level exception with reply code 403 (ACCESS_REFUSED).

[ray zuniga]

David,

I read the section. some followup questions.

1. They have shown me configs are not declaring the queue statically (auto generated),

   1.b queues auto-delete + exclusive features

2. This error is intermittent.....this tells me if they were trying to create queue with amq prefix would mean it never works.. this is not the case, they  work 99 % of the time

This is what leads me to believe its a reconnect logic issue where they are taking the name after generation and passing it back for reconnect which then leads to the error.

I hope this makes sense.

Thanks for the responses

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/9f6fd2bb-8b06-41d4-a75f-668cb23ac0b9n%40googlegroups.com.

[Ravi Hara]

That's right. The rabbitmq gives autogenerated queue name if we do not provide the name explicitly. As mentioned by Ray, this is intermittent and looks like some gap with the documentation and the actual Rabbitmq behaviour.