4 Replies Latest reply on Jul 15, 2015 6:20 AM by jaikiran pai

    Failed to parse configuration in WildFly 9 Final

    Raj Kumar Newbie

      Hi, Am Configuring MySql Driver in standalone.xml file, i got this Exception when am trying to restart wildfly.

       

      Here is Driver which i have added unders <drivers> tag in standalone.xml file in wildfly 9 Final

       

      <driver name="mysql" module="com.mysql">

      <xa-datasource-class>com.mysql.jdbc.Driver</xa-datasource-class>

      </driver>

       

      Log :

       

      2015-07-15 01:55:47,285 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

              at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112)

              at org.jboss.as.server.ServerService.boot(ServerService.java:331)

              at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:259)

              at java.lang.Thread.run(Thread.java:745)

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,1]

      Message: Unexpected element '{urn:jboss:domain:3.0}server'

              at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)

              at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)

              at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104)

              ... 3 more

      2015-07-15 01:55:47,286 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

      2015-07-15 01:55:47,300 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss WildFly Full 9.0.0.Final (WildFly 8.2.0.Final) stopped in 4ms

       

      After removing the above tag and restarted the server, but same exception is occuring.

      can any one have an idea ? what is the cause of this Exception ?

       

      Thank you,

       

      Rajkumar

        • 1. Re: Failed to parse configuration in WildFly 9 Final
          jaikiran pai Master

          2015-07-15 01:55:47,300 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss WildFly Full 9.0.0.Final (WildFly 8.2.0.Final) stopped in 4ms

          Slightly off topic, is this really the log message you are seeing? I'm surprised by 2 things here - one it calls it "JBoss WildFly" and second it shows WildFly 8.2.0.Final instead of the WildFly core version number.

          • 2. Re: Failed to parse configuration in WildFly 9 Final
            Wolfgang Mayer Master

            It looks like standalone reads the domain.xml instead.

            I understand also that com.mysql.jdbc.Driver is not a XA driver.

            You may use com.mysql.jdbc.jdbc2.optional.MysqlXADataSource instead.

            • 3. Re: Failed to parse configuration in WildFly 9 Final
              Raj Kumar Newbie

              Thanks JaiKiran,

               

              As per my observation, i got to knew the cause of issue may be that " we have replaced modules folder of WildFly 8.2.0 with WildFly 9.0.0,.

               

              As earlier we have used wildfly 8.2.0 which was working fine, we we are migrating server to WildFly 9,

               

              May be the WildFly 9 is not loading WildFly 8 Modules, need to revert back and check.

              • 4. Re: Failed to parse configuration in WildFly 9 Final
                jaikiran pai Master

                Raj Kumar wrote:

                 

                Thanks JaiKiran,

                 

                As per my observation, i got to knew the cause of issue may be that " we have replaced modules folder of WildFly 8.2.0 with WildFly 9.0.0,.

                 

                ...

                May be the WildFly 9 is not loading WildFly 8 Modules, need to revert back and check.

                So the way you installed WildFly 9.0.0.Final is more like you patched any existing WildFly 8.2.0.Final by copy/pasting the modules folder? I wouldn't recommend doing it. The right way to do it is, unzip/untar the new WildFly 9.0.0.Final installation to a new location and if you have a custom standalone/domain configuration xml in a previous version, just use that configuration in the new WildFly 9.0.0.Final.