The code used to parse a domain.xml file was incorrectly validating that all runtime-name configuration values were unique across all deployments in the domain. This was incorrect, as these values only need to be unique within a set of deployments mapped to a server group. Using two deployments with the same runtime-name in the domain (for example, two different versions of the same deployment) would result in a fatal boot error if the domain controller was restarted, with output like this in the host controller log: 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 'foo' has already been declared The scope of XML parser validation of runtime-name uniqueness has been limited to an individual server group. Post-parsing validation of the management configuration model has also been improved to exclude deployments marked as not enabled. Restarting a domain controller whose config includes two deployments with the same runtime-name now works.