[rabbitmq-discuss] Weird Crash (1M to 10M messages over STOMP?) - Recovery logic for durable messages/queues/exchanges?

Matthias Radestock matthias at lshift.net
Fri Aug 7 22:39:14 BST 2009


Darien Kindlund wrote:
> Back to the main crash issue.  It happened again.  The short version:
> This crash may have to do with sending large messages over STOMP --
> I'm not sure.  I've proposed a couple of unit test cases below and am
> curious if you're able to replicate the issue, based upon those tests.

I forgot you were one of the STOMPers ;)

That opens up a new direction of investigation.

> Here's the details:
> 1) Primary indication that RabbitMQ died, is when issuing a
> 'rabbitmqctl' command:
> # rabbitmqctl list_exchanges
> Listing exchanges ...
> Error: {badrpc,nodedown}
> 2) Listing all the erlang relevant processes shows just this:
> # ps ax | grep erla
> 14488 ?        S      0:00 /usr/lib/erlang/erts-5.5.5/bin/epmd -daemon

ok. Looks like the rabbit had indeed perished.

> Then, I checked the /var/log/rabbitmq/startup_log file, which showed:
> [...]

Can you send me a copy of the rabbit.log?

> Is there some sort of (implicit) upper limit on the allowable message
> size when sending over STOMP?

Not that I am aware of.

> I'm sending you a copy of the mnesia directory in a separate
> email directly to you. 

When I recover that into my local rabbit instance I get a whole bunch of 
exchanges, queues and bindings, but no messages - unacknowledged or 
otherwise. Do you see something different?



More information about the rabbitmq-discuss mailing list