[rabbitmq-discuss] Wrong behaviour with large memory amounts in Windows

Germán Latorre german.latorre at twindocs.com
Mon Jun 21 07:54:40 BST 2010

Hello Mathew,

It's true that our Erlang version is not the last one... It's R12B.  
We'll try with its latest stable release.

And yes, I think we'll run it under Linux in our live environment.  
We'll try with new persister branch too.

Thank you very much for your help.


Germán Latorre.

El 18/06/2010 15:58, Matthew Sackman escribió:
> Germán,
> On Fri, Jun 18, 2010 at 02:32:00PM +0100, Matthew Sackman wrote:
>> On Fri, Jun 18, 2010 at 03:02:58PM +0200, Germán Latorre wrote:
>>> Here is the log with vm_memory_high_watermark set to 2:
>>> =WARNING REPORT==== 14-Jun-2010::15:57:40 ===
>>> Unknown total memory size for your OS {win32,nt}. Assuming memory
>>> size is 1024MB.
>> That entry shouldn't occur - it should be happy to detect 32-bit
>> windows. This suggests you're running a version of Rabbit older than
>> 1.7.2. I would suggest upgrading if you can.
> Actually, I've just reread that area of the code. Even with the latest
> Rabbit, that can still happen if your version of Erlang is sufficiently
> old. You'd need to be using at least Erlang R13B for that problem to be
> solved, and generally we'd recommend the latest stable Erlang release
> (R13B04 is currently it). That at least would fix the erroneous memory
> detection under Windows, but if you're able to use a Linux instead, it
> rather renders the point moot.
> Matthew

Germán Latorre Antín
Principal Software Engineer
TwinDocs - https://www.twindocs.com
(+34) 902 523 232

More information about the rabbitmq-discuss mailing list