[rabbitmq-discuss] RabbitMQ 2.2.0 message delivery issue: internal crash

Matthias Radestock matthias at rabbitmq.com
Thu Aug 18 17:41:52 BST 2011


On 18/08/11 14:50, Alfonso Pantoja wrote:
> Because this issue does not happen very ofter I'm wondering if you
> could suggest what to the check (messages properties use, etc.) or the
> possible causes that lead to message corruption (after reading your
> responses I  understand that we should review our modifications in
> mod_rabbitmq but it would be nice to have a tip to track down that
> bug)

In the original rabbitmq-xmpp code base, the only place for things to go 
wrong is at 
That code is bullet proof (famous last words), but I suspect you have 
either modified it or have similar code elsewhere.

The thing to watch out for in particular is what values you place in the 
properties. Their type must correspond to what is expected for the given 
key in the Basic content properties (see 
http://www.rabbitmq.com/amqp-0-9-1-reference.html#class.basic). shortstr 
and longstr must be Erlang binaries. octet, shortint, longint, 
longlongint and timestamp must be Erlang integers. And 'table' must be a 
list of {KeyBinary, TypeAtom, Value}.

> Regarding the broker upgrade I would like to know what is the
> procedure for upgrading it without losing the messages (all our
> messages are persistent).

Simply install the new broker. Persistent messages in durable queues 
will be retained.


More information about the rabbitmq-discuss mailing list