[jboss-jira] [JBoss JIRA] (WFLY-5330) Can't start managed domain in --admin-only with EAP 6.4 configuration

[Kabir Khan (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan closed WFLY-5330.
----------------------------


> Can't start managed domain in --admin-only with EAP 6.4 configuration
> ---------------------------------------------------------------------
>
>                 Key: WFLY-5330
>                 URL: https://issues.jboss.org/browse/WFLY-5330
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 10.0.0.Beta2
>            Reporter: Ladislav Thon
>            Assignee: Stuart Douglas
>            Priority: Critical
>             Fix For: 10.0.0.CR1
>
>
> When starting WildFly 10.0.0.Beta2 managed domain in {{--admin-only}} mode to perform {{:migrate}} operations on old subsystems \[1\], using an unmodified {{domain.xml}} and {{host.xml}} configuration files from EAP 6.4.0, I'm getting errors \[2\].
> Apparently, the domain configuration files in EAP 6.4 still contain the {{configadmin}} extension and subsystems. The standalone configuration files from EAP 6.4 no longer contain that, which is why this problem wasn't found earlier and wasn't described in WFLY-5092.
> Based on http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004306.html, I'm expecting that I don't have to perform any changes to the EAP 6.4 configuration files.
> \[1\]
> {code}
> unzip jboss-eap-6.4.0.zip
> unzip wildfly-10.0.0.Beta2.zip
> rm wildfly-10.0.0.Beta2/domain/configuration/*.xml
> cp jboss-eap-6.4/domain/configuration/domain.xml wildfly-10.0.0.Beta2/domain/configuration/
> cp jboss-eap-6.4/domain/configuration/host.xml wildfly-10.0.0.Beta2/domain/configuration/
> ./wildfly-10.0.0.Beta2/bin/domain.sh --admin-only
> {code}
> \[2\]
> {code}
> [Host Controller] 09:21:47,835 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> [Host Controller] 	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> [Host Controller] 	at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:673)
> [Host Controller] 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:272)
> [Host Controller] 	at java.lang.Thread.run(Thread.java:745)
> [Host Controller] Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.configadmin
> [Host Controller] 	at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:155)
> [Host Controller] 	at org.jboss.as.host.controller.parsing.DomainXml_Legacy.readDomainElement2_0(DomainXml_Legacy.java:377)
> [Host Controller] 	at org.jboss.as.host.controller.parsing.DomainXml_Legacy.readElement(DomainXml_Legacy.java:133)
> [Host Controller] 	...
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)