Problem

The sandbox processes keeps running on an instance after the stop-confluence.sh script was already executed. When the stop-confluence script reached the time limit and called the shutdown.sh 20 -force which kills the primary Confluence process but keeps the children still running.

Suggested Solution

When forcefully stopping Confluence after the attempt to gracefully do it should should also kill the child processes.

Why This Is Important

Orphaned processes in an environment can cause performance degradation and resource wastage on a host.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available