Dear Matthew,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm afraid it's still not quite ready. Most of the core work is done and</blockquote>
<div><br>it's not a trivial problem, and it'll be such a cool feature! I guess it's wishful hearing that made me think it's ready :)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can you check the logs and say whether you get alarm high_water_mark<br>
type messages in there? Also, in these cases, does free, or similar,<br>
show pretty much no free RAM? Also, does a ball park calcualation of<br>
message size * 200000 give you about your amount of RAM (within a factor<br>
of 2)?<br></blockquote></div><br>could you offer a rule of thumb for calculating the AMQP message size? I am sending lists of 5-10 ASCII characters. Judging from the disk space consumed by the mnesia directory, however, I think it's possible we are exhausting the RAM, if all messages are also kept in memory. And yes, just before the vm crashes, free shows little memory left (~150Mb), there is a little bit of lag between reaching this amount and the crash, it's a little hard to tell because rabbitmq runs on the database server and there are other programs running as well. There's no indication of any problems in the logs, except <br>
<br>=SUPERVISOR REPORT==== 1-Jul-2009::15:46:06 ===<br> Supervisor: {local,rabbit_sup}<br> Context: shutdown_error<br> Reason: shutdown<br> Offender: [{pid,<0.142.0>},<br> {name,rabbit_persister},<br>
{mfa,{rabbit_persister,start_link,[]}},<br> {restart_type,transient},<br> {shutdown,100},<br> {child_type,worker}]<br><br>in rabbit-sasl.log (but the vm definetly dies)<br>
<br>cheers, Michael<br><br>