Problems When RabbitMQ in SystemLink Server Can't Find Handle.exe

Issue Details

I am seeing one of the following problems with my SystemLink Server:

• The RabbitMQ logs state that it is shutting itself down due to a lack of available RAM, when in fact plenty of RAM is available
• A growing number of Erlang Powershell processes appear stalled in Windows Task Manager, consuming ever more RAM
• Erlang Runtime (erl.exe) makes API calls to CreateFile that appear in the process manager logs, concerning observers in IT

Solution

Additional Information

RabbitMQ running on Windows is designed to use handle.exe. If handle.exe is not present in the Windows PATH, RabbitMQ attempts to locate it. If it cannot be found, RabbitMQ falls back to using PowerShell. During this discovery and decision process, PowerShell CreateFile API calls are issued as part of the search and validation logic against:

• System directories
• Directories included in the Windows PATH

    
These CreateFile calls are performed solely for discovery and verification purposes and are part of the normal execution flow.

If RabbitMQ can't find handle.exe, it can return incorrect memory usage values, which can cause RabbitMQ to shut itself down.