[rabbitmq-discuss] Bug/Behavior Change in binds to header exchanges in rabbitmq 3.1.0

Matthias Radestock matthias at rabbitmq.com
Tue May 7 10:48:22 BST 2013


On 06/05/13 21:56, Andrew Miller wrote:
> I also ran into this behavior when updating my brokers today.  However,
> the change was a little more mysterious, as I had persistent queues
> setup with existing bindings from 3.0.2.  Instead of seeing any
> information about requiring x-match header on the queue bindings, I
> instead just received the following client error when trying to publish
> to the exchange:

Ah yes. We forgot to consider upgrades. Sorry. Have filed a bug to look 
into that.


More information about the rabbitmq-discuss mailing list