The domain.conf file adds debug configuration to $JAVA_OPTS. That's incorrect, as it results in the same debug config being applied to the ProcessController and HostController processes, leading to port conflicts. A launch command something like this might work:

eval \"$JAVA\" $JAVA_OPTS \
\"-Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/process-controller/boot.log\" \
\"-Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties\" \
$PROCESS_CONTROLLER_DEBUG_OPTS \
-jar \"$JBOSS_HOME/jboss-modules.jar\" \
-mp \"$JBOSS_HOME/modules\" \
-logmodule "org.jboss.logmanager" \
org.jboss.as.process-controller \
-jboss-home \"$JBOSS_HOME\" \
-jvm \"$JAVA\" \
– \
\"-Dorg.jboss.boot.log.file=$JBOSS_HOME/domain/log/host-controller/boot.log\" \
\"-Dlogging.configuration=file:$JBOSS_HOME/domain/configuration/logging.properties\" \
$HOST_CONTROLLER_DEBUG_OPTS \
$JAVA_OPTS \
– \
-default-jvm \"$JAVA\" \
"$@"

$PROCESS_CONTROLLER_DEBUG_OPTS and $HOST_CONTROLLER_DEBUG_OPTS would be new variables set in domain.conf.