[rabbitmq-discuss] Program crashes in amqp_abort() on HP-UX 11.31

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Mon Jul 8 13:46:08 BST 2013


On 8 July 2013 03:11, Haster <haster2004 at yandex.ru> wrote:

> Failed to start consumer with configurationInternal error: invalid
> amqp_connection_state_t->state 0

This is not necessarily the result of a corrupted packet, but it is the
result of some kind of memory corruption or threading bug. (It could also
be a bug in the library.)

There is nothing sensible you can do to recover: memory is already
corrupted, possibly extensively. There's no way to know. Calling abort() is
the right thing to do in this situation.

If you are using an amqp_connection_state_t from multiple threads, you
should either mutex access to it (difficult) or create a separate
connection for each thread (easier).

Tony Garnock-Jones
tonygarnockjones at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130708/a6d70f05/attachment.htm>

More information about the rabbitmq-discuss mailing list