Run::execute:

1. start a broker
2. add several external components while starting them right after

If the broker is getting started and, right before activating, throw an exception (eg on NodeManager::start), its process won't be stopped because the ActivationFailureListener won't get triggered.

if the broker is getting started and, right before activating it, it throws an exception AND raise an I/O critical error (eg JdbcNodeManager:.start), a separate Thread would race to stop the broker external components while they are being added (and started): if some of these components are added AFTER the stop has completed or are started after being stopped, they would prevent the process to stop.