Back to bug 1039699
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jimmy Wilson | 2013-12-09 21:22:51 UTC | CC | jawilson | |
| Blocks | 1027004 | |||
| Jimmy Wilson | 2013-12-09 21:23:14 UTC | Target Release | --- | EAP 6.2.CP0a |
| Brad Maxwell | 2013-12-10 06:26:48 UTC | CC | bmaxwell | |
| Brian Stansberry | 2013-12-11 00:27:21 UTC | Link ID | JBoss Issue Tracker WFLY-2633 | |
| Brian Stansberry | 2013-12-11 17:34:16 UTC | Blocks | 1040621 | |
| Brian Stansberry | 2013-12-11 17:35:41 UTC | Blocks | 1040621 | |
| Brian Stansberry | 2013-12-11 17:36:17 UTC | Depends On | 1040621 | |
| Brian Stansberry | 2013-12-11 17:42:25 UTC | Status | NEW | POST |
| Brian Stansberry | 2013-12-13 19:55:18 UTC | Target Release | EAP 6.2.CP0a | EAP 6.2.1 |
| mark yarborough | 2013-12-17 01:47:17 UTC | CC | myarboro | |
| Jimmy Wilson | 2014-01-07 14:40:39 UTC | CC | tim.einmahl | |
| Blocks | 1040681 | |||
| Carlo de Wolf | 2014-01-08 15:03:32 UTC | Status | POST | MODIFIED |
| CC | cdewolf | |||
| mark yarborough | 2014-01-13 14:15:40 UTC | Summary | Cannot use deployments with same runtime-name in a domain | [GSS] (6.2.x) Cannot use deployments with same runtime-name in a domain |
| Carlo de Wolf | 2014-01-16 15:13:36 UTC | Target Milestone | --- | CR1 |
| Scott Mumford | 2014-01-20 00:21:21 UTC | CC | smumford | |
| Brian Stansberry | 2014-01-20 15:55:18 UTC | Doc Text | Cause: The parsing 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. Consequence: 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 Fix: 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. Result: Restarting a domain controller whose config includes two deployments with the same runtime-name now works. |
|
| Vaclav Tunka | 2014-01-20 22:17:40 UTC | Status | MODIFIED | ON_QA |
| Scott Mumford | 2014-01-22 00:28:13 UTC | Doc Text | Cause: The parsing 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. Consequence: 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 Fix: 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. Result: Restarting a domain controller whose config includes two deployments with the same runtime-name now works. | 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. |
| Nikoleta Hlavickova | 2014-01-24 08:49:11 UTC | Status | ON_QA | VERIFIED |
| CC | nziakova | |||
| mark yarborough | 2014-02-24 20:14:16 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-02-24 15:14:16 UTC |
Back to bug 1039699