Issue Summary

During a shutdown command with stop-confluence.sh/stop-confluence.bat, if it's not possible to gracefully shut down the Confluence process and its children (any running sandbox) in 20 seconds, the script will kill the Confluence process by its PID, which can leave the child processes still running. This can cause performance degradation and resource wastage on a host, as these processes will stay running until manually killed by an administrator, by the OS, or by a server shutdown.

Expected Results

Any processes created by Confluence ideally must be handled by it throughout their entire lifetime, from start to termination.

Actual Results

Orphaned sandboxes can be seen running in the OS after Confluence has been shut down.

Workaround

Manually shutdown the orphaned sandbox processes using Kill(or similar) commands.