[rabbitmq-discuss] 406 precondition-failed vs 530 not-allowed on exchange declaration

Matthias Radestock matthias at rabbitmq.com
Fri Jul 8 09:45:08 BST 2011


On 08/07/11 09:36, Michael Klishin wrote:
> An amqp gem user reported seeing 530 not-allowed connection exception
> when declaring an exchange. The error message is
> «NOT_ALLOWED - cannot redeclare exchange 'jobs' in vhost '/' with
> different type, durable or autodelete value»
> Do I understand it correctly that this is a permissions issue? We have
> plenty of examples of faulty exchange declaration in the amqp gem test
> suite,
> but they all result in 406 precondition-failed.

That user must be running an ancient broker, probably pre-2.0.0. The 
error is likely exactly what it says, and not a permission issue. the 
spec was unclear on some of the error codes, so older rabbits returned 
not_allowed in some of these cases. Recent rabbits will return 


More information about the rabbitmq-discuss mailing list