[rabbitmq-discuss] Postponed queues declaration problem after updating to latest version

Matthias Radestock matthias at rabbitmq.com
Sun Jul 14 16:57:29 BST 2013


On 14/07/13 15:14, Adam Markovski wrote:
> Before updating to latest Rabbit version (3.1.3 release) for each queue
> we were declaring postponed queue (for delayed messaged) using the
> x-dead-letter-exchange and x-message-ttl attributes, binding with the
> specific types needed.
> After the updating, I'm trying the same thing using the newest client
> but without success. It is fine while defining the queue for the first
> message type, but it fails for the second next, with the exception:
>     Exception occured starting the MQ Agent:
>     RabbitMQ.Client.Exceptions.OperationIn
>     terruptedException: The AMQP operation was interrupted: AMQP
>     close-reason, initi
>     ated by Peer, code=406, text="PRECONDITION_FAILED - inequivalent arg
>     'x-dead-let
>     ter-exchange'for queue 'emr-agent-queue_postponded' in vhost '/':
>     received the v
>     alue 'Common.Agent.Messages.MQ.FileRequest' of type 'longstr' but curr
>     ent is the value 'Common.Agent.Messages.MQ...", classId=50, methodId=10
> Has anyone had similar problems?

I suspect you are attempting to declare the queue with different 
x-dead-letter-exchange values. Take a look at the server log since it 
will contain the full error message rather than the truncated version above.

iirc nothing has changed in the server or client recently regarding this 


More information about the rabbitmq-discuss mailing list