Good day,<div><br></div><div>We are running in a problem while deploying a new cluster. �The one node (dev) cluster is running RabbitMQ 2.71. �We got some Perl Net::AMQP clients that connect to the cluster and subscribes to a queue. �The clients are existing with an error, usually after consuming a handful of messages. �The error is "No way to unpack field 'redelivered' type 't'".�</div>
<div><br></div><div>It seems the client is dying while unpacking the redelivered field in a message delivery command. �The Net::AMQP client only supports the 0-8 protocol. �I've verified that RabbitMQ believes the client is connected using AMQP 0-8. �My guess is that RabbitMQ is sending the client a 0-9-1 formated message, instead of a 0-8 message. �The "redelivered" field does not appear to be defined in 0-8, and its type in 0-9-1 is boolean or "t", which is also not defined in 0-8. �Thus, Net::AMQP is throwing an error when it finds a field of an unknown type.</div>
<div><br></div><div>The client's owner claims the client has worked successfully against the same messages we are feeding it on a 2.5.1 cluster. �So we are wondering if something changed between 2.5.1 and 2.7.1 that may cause this behavior.</div>
<div><br></div><div>We've also tested queues as both HA and non-HA and observe the same problem (we figured it may be related to the new HA code since we we had configured them as HA queues).</div><div><br></div><div>
We are going to start downgrading the cluster one version at a time towards 2.5.1 to determine whether some version does not exhibit the problem.</div><div><br></div><div>RabbitMQ folks, any suggestions?</div><div><br></div>
<div>Elias Levy</div>