This article describes how to work around the fact that Microsoft Windows doesn't allow more than 68 runtime sessions at a time.
acurcl appears to "hang" when users attempt to start more than 68 runtime processes at the same time using Micro Focus Thin Client version 7.2.2 on Windows 2000.
Investigation revealed that this problem is the result of a Microsoft Windows limitation. A Microsoft Knowledge Base article, #814802, describes this issue. The article provides information about modifying the registry to allow more runtimes to run. However, this modification may adversely affect other services running on a server, so we strongly suggest that users read and understand that article before attempting to modify the registry entry.
The registry entry to modify isHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems
and the value to modify is "Windows".
The default value of this entry is:
SharedSection=1024,3072,512 Windows=On SubSystemType=Windows
and the relevant part of this entry is "SharedSection=1024,3072,512".
Note that the server must be rebooted before the new settings take effect. Also note that modifying the registry is inherently dangerous and should be done with caution.
There is a way to detect whether you have reached this limitation: When the Windows version of acurcl starts a new child runtime, it will wait a short while (50 milliseconds) to see if the child stops. If the child stops, that fact will be reflected in the trace file, along with the exit code of the child. An exit code of 128 is the magic value that says that this limitation of Windows has been encountered. (This test was introduced in ECN-AC050.)
Incident Number: 99-015708 and 2260289