In versions prior to 8.1.2 and when using Thin Client, if the runtime on the server side was stuck in a process intensive loop, then issuing the acurcl -kill -p command had no effect until the runtime became free to process the kill command. This lead to orphan runtimes as sometimes the runtime never came out of the loop or became free and also a hard kill command was never issued.
This behaviour was corrected in version 8.1.2 so that after a default set amount of time, a hard kill command is issued on the errant runtime.
The amount of time to wait before a hard kill is issued can be controlled by the FORCE_KILL_TIME. Set this variable to the amount in seconds to wait before issuing a hard kill. The default value for this variable is 150 seconds