|
|
|
When FairCom Server shuts down, it waits for a period of time for internal threads to terminate. If the time limit is reached and a thread hasn't terminated, the server logs a message to CTSTATUS.FCS indicating this situation (for example, "ctDISKFULLaction thread still running").
A potential problem was that, if internal threads are still running at the end of server shutdown, the server still freed some resources that the threads might be using (such as memory suballocator lists). This could cause the server to crash at the end of shutdown.
To avoid this possibility, we now track the number of threads that are still running, and if at least one thread is still running, we skip freeing the resources.
