The check for duplicate runtime-name in a server group on startup is too aggressive. It is incorrectly throwing an error on startup if there are any duplicate runtime-names in the whole domain, instead of just in a single server group.

Steps to Reproduce:

1. Start a single HC/DC
2. deploy --name=foo1 --runtime-name=bar --disabled testfile
3. deploy --name=foo2 --runtime-name=bar --disabled testfile
4. restart the DC/HC

Actual results:

JBAS010932: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1348,9]
...
Message: JBAS014664: An element of this type named 'bar' has already been declared

Expected results:

No errors