When ArquillianService installs a service for an ArquillianConfig it is not ensuring that service names are unique. When it builds the service name it only accounts for the name of the deployment/subdeployment, ignoring the fact that subdeployments with different parents can have the same name. It should check if the deployment is a subdeployment and if so include the parent deployment name in the service name.

It currently works around this with a hack in ArquillianConfigBuilder: see the code following the FIXME in https://paste.fedoraproject.org/525756/58138148/

Presumably the answer to the FIXME's question is my first paragraph here.

The hack should be removed as part of fixing this; it's verboten to block an MSC service thread, which this hack does.