Back to bug 1040621
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brian Stansberry | 2013-12-11 17:34:55 UTC | Target Release | EAP 6.2.CP0a | EAP 6.3.0 |
| Blocks | 1027004 | |||
| Brian Stansberry | 2013-12-11 17:35:41 UTC | Depends On | 1039699 | |
| Brian Stansberry | 2013-12-11 17:36:17 UTC | Blocks | 1039699 | |
| Brian Stansberry | 2013-12-11 17:50:55 UTC | Status | NEW | POST |
| Kabir Khan | 2014-01-07 13:26:13 UTC | Status | POST | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | DR1 | ||
| Kabir Khan | 2014-01-08 12:04:21 UTC | Target Milestone | DR1 | DR0 |
| mark yarborough | 2014-01-13 14:16:41 UTC | CC | myarboro | |
| Summary | Cannot use deployments with same runtime-name in a domain | [GSS] (6.3) Cannot use deployments with same runtime-name in a domain | ||
| Paul Gier | 2014-02-11 23:53:25 UTC | Status | MODIFIED | ON_QA |
| Petr Kremensky | 2014-02-24 14:28:20 UTC | Status | ON_QA | VERIFIED |
| Brian Stansberry | 2014-06-03 14:54:38 UTC | Doc Text | Cause: The check for duplicate values for deployment runtime-name attributes 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. Consequence: Including multiple deployments in a domain with the same runtime-name will result in a boot failure even if those deployments are not mapped to the same server group. For example: 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 'example.war' has already been declared Fix: The validation of uniqueness of runtime names was moved from the xml parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group. Result: Multiple deployments with the same runtime-name value can coexist in a domain so long as they are not mapped to the same server group. |
|
| Brian Stansberry | 2014-06-03 16:22:32 UTC | Doc Text | Cause: The check for duplicate values for deployment runtime-name attributes 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. Consequence: Including multiple deployments in a domain with the same runtime-name will result in a boot failure even if those deployments are not mapped to the same server group. For example: 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 'example.war' has already been declared Fix: The validation of uniqueness of runtime names was moved from the xml parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group. Result: Multiple deployments with the same runtime-name value can coexist in a domain so long as they are not mapped to the same server group. | Cause: The check for duplicate values for deployment runtime-name attributes in a server group on startup was too aggressive. It was incorrectly throwing an error on startup if there were any duplicate runtime-names in the whole domain, instead of just in a single server group. Consequence: Including multiple deployments in a domain with the same runtime-name will result in a boot failure even if those deployments are not mapped to the same server group. For example: 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 'example.war' has already been declared Fix: The validation of uniqueness of runtime names was moved from the xml parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group. Result: Multiple deployments with the same runtime-name value can coexist in a domain so long as they are not mapped to the same server group. |
| Scott Mumford | 2014-06-04 02:23:22 UTC | CC | smumford | |
| Doc Text | Cause: The check for duplicate values for deployment runtime-name attributes in a server group on startup was too aggressive. It was incorrectly throwing an error on startup if there were any duplicate runtime-names in the whole domain, instead of just in a single server group. Consequence: Including multiple deployments in a domain with the same runtime-name will result in a boot failure even if those deployments are not mapped to the same server group. For example: 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 'example.war' has already been declared Fix: The validation of uniqueness of runtime names was moved from the xml parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group. Result: Multiple deployments with the same runtime-name value can coexist in a domain so long as they are not mapped to the same server group. | In previous versions of JBoss EAP 6, the check for duplicate values for deployment runtime-name attributes in a server group on startup was too aggressive. It was incorrectly throwing an error on startup if there were any duplicate runtime-names in the whole domain, instead of just in a single server group. As a result, including multiple deployments in a domain with the same runtime-name would result in a boot failure even if those deployments are not mapped to the same server group. For example: ---- 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 'example.war' has already been declared ---- In this release the validation of uniqueness of runtime names was moved from the XML parser to the operation execution logic, and the validation logic was adjusted to ignore duplicates not associated with the same server group. Multiple deployments with the same runtime-name value can now coexist in a domain so long as they are not mapped to the same server group. |
||
| mark yarborough | 2014-06-28 15:26:24 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:26:24 UTC |
Back to bug 1040621