Ladislav Thon created WFCORE-1517:
-------------------------------------
Summary: can't start server with configuration file from EAP 6.4.7 (and
above)
Key: WFCORE-1517
URL:
https://issues.jboss.org/browse/WFCORE-1517
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Ladislav Thon
Assignee: Brian Stansberry
Priority: Blocker
When trying to run EAP 7 with a configuration file from EAP 6.4.7 (i.e. management version
1.8), presumably for migration, the server fails to boot with an error message like this:
{code}
14:44:44,305 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught
exception during boot:
org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed
to parse configuration
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
[wildfly-controller-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
at org.jboss.as.server.ServerService.boot(ServerService.java:356)
[wildfly-server-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
[wildfly-controller-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,1]
Message: Unexpected element '{urn:jboss:domain:1.8}server'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
[staxmapper-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
[staxmapper-1.2.0.Final-redhat-1.jar:1.2.0.Final-redhat-1]
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
[wildfly-controller-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
... 3 more
14:44:44,306 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot
has failed in an unrecoverable manner; exiting. See previous messages for details.
{code}
This is really because the {{org.jboss.as.controller.parsing.Namespace}} enum doesn't
have a constant for management version 1.8. After fixing that, everything seems to work
fine (I guess that the rest of the server is fully aware of mgmt version 1.8), so this was
hopefully just this single omission.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)