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

Andrew Miller andrew.miller at sentry.com
Mon May 6 21:56:53 BST 2013


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:
 
RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP 
operation was interrupted: AMQP close-reason, initiated by Peer, code=541, 
text="INTERNAL_ERROR", classId=0, methodId=0, cause=
   at RabbitMQ.Client.Impl.SimpleBlockingRpcContinuation.GetReply()
   at RabbitMQ.Client.Impl.ModelBase.ModelRpc(MethodBase method, 
ContentHeaderBase header, Byte[] body)
   at RabbitMQ.Client.Framing.Impl.v0_9_1.Model.TxCommit()
 
and on the broker, saw the following:
 
=ERROR REPORT==== 6-May-2013::15:33:54 ===
** Generic server <0.445.0> terminating
** Last message in was {'$gen_cast',
...
** Reason for termination == 
** {{{badmatch,undefined},
     [{rabbit_exchange_type_headers,headers_match,2,[]},
      {rabbit_router,'-match_bindings/2-fun-1-',10,[]},
      {qlc,collect,1,[{file,"qlc.erl"},{line,1328}]},
      {qlc,eval,2,[{file,"qlc.erl"},{line,296}]},
      {mnesia_tm,non_transaction,5,[{file,"mnesia_tm.erl"},{line,734}]},
      {rabbit_exchange,route1,3,[]},
      {rabbit_exchange,route,2,[]},
      {rabbit_channel,handle_method,3,[]}]},
    [{mnesia_tm,non_transaction,5,[{file,"mnesia_tm.erl"},{line,747}]},
     {rabbit_exchange,route1,3,[]},
     {rabbit_exchange,route,2,[]},
     {rabbit_channel,handle_method,3,[]},
     {rabbit_channel,handle_cast,2,[]},
     {gen_server2,handle_msg,2,[]},
     {proc_lib,wake_up,3,[{file,"proc_lib.erl"},{line,237}]}]}
 
I saw nothing in the release notes to indicate that this was an intended 
change.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130506/90d15887/attachment.htm>


More information about the rabbitmq-discuss mailing list