Matthias,<div><br></div><div>Your are right Windows have a limitation to memory allocation per process, and some versions of Windows is 2Gb the limitation, a long time ago I have a lot of problems with it.</div><div><br></div>
<div>I don't know what type of windows John are using but this is a link of Microsoft to talk about this limitations in all versions of windows.</div><div><br></div><div><a href="http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx">http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx</a></div>
<div><br></div><div>Regards.</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Jan 26, 2010 at 5:32 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">John,<br>
<div class="im"><br>
John Apps wrote:<br>
> Here are two runs, one with 0.4 and the other, below, with 0.3. Both<br>
> crash. The rabbit.log for the 0.3 test is attached. The 0.4 test did not<br>
> log any memory watermark messages, only the 0.3 test.<br>
<br>
</div>I cannot see any memory alerts in the 0.3 test log either.<br>
<br>
The earlier 0.2 log, showed a limit of 817MB and a max value of ~1.3G.<br>
Assuming those ratios are similar for the 0.3 case (1225MB), it would<br>
indicate the O/S isn't happy with Rabbit asking for more than ~2GB of<br>
memory.<br>
<br>
Some quick googling on Erlang under Windows suggests that 2GB may in<br>
fact be a limit imposed by some flavours of Windows. Different flavours<br>
have different limits; somebody more familiar with Windows might be able<br>
to provide more precise information.<br>
<br>
I guess you'll have to stick to a limit of 0.2, or perhaps try 0.25.<br>
<br>
> />>>That's exactly what is supposed to happen. Rabbit has told the<br>
<div class="im">> producer to stop sending messages since it is under memory pressure.<br>
> Once memory becomes available again, e.g. when a consumer consumes<br>
> enough messages, or some queues get deleted/purged, or as a result of<br>
> internal garbage collection, Rabbit will tell the producer that it may<br>
> resume.<br>
> /<br>
><br>
> The funny thing is that rabbitmqctl status returned a 'node down'<br>
> message. I suppose that is OK?<br>
<br>
</div>No, that's not ok. Presumably rabbitmqctl normally works fine, right?<br>
<br>
Next time this happens, please do the following:<br>
- capture & report the complete output of rabbitmqctl<br>
- check whether the rabbit process is alive<br>
- assuming it is, report whether it's busy or idle<br>
- terminate the test program<br>
- try running rabbitmqctl again and report the results<br>
- post the complete rabbit.log and rabbit-sasl.log<br>
<div><div></div><div class="h5"><br>
<br>
Regards,<br>
<br>
Matthias.<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>