[rabbitmq-discuss] Java client Channel.Close blocking indefinitely

[Emile Joubert]

Hi Iain,

On 01/09/11 12:04, Iain Hull wrote:
> On 01/09/11 09:06, Matthias Radestock wrote:
>> [as an aside, it is curious that the limit for the erlang processes is
>> reported as 32k - the default rabbit config sets it to 1M; have you 
>> changed the config / start up scripts?]
> That is strange I am currently running 2.6.0 on windows without a config
> file.  I also have 8 Gb of ram but I am running 32 bit erlang, so maybe
> that explains the low 819.2MB high watermark.  Production will running
> on CentOS with 24 Gb or 32 Gb of ram and I expect to increase the
> vm_memory_high_watermark to use most of this.

It turns out that when running as a windows service we don't raise the
process limit from the default of 32k to 1M. I will file a bug to fix
that. In the meantime you can either run rabbit as an application or add
the "+P 1048576" erl argument to rabbitmq-service.bat manually until
that fix gets released.

You should be aware that there are some differences between the Windows
and Unix Erlang VMs. The Windows VM is 32bit and limited to 2GB RAM.


-Emile