-
1. Re: Failed to parse configuration in WildFly 9 Final
jaikiran Jul 15, 2015 4:29 AM (in response to samalaraj72)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
mayerw01 Jul 15, 2015 4:55 AM (in response to samalaraj72)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
samalaraj72 Jul 15, 2015 6:14 AM (in response to jaikiran)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 Jul 15, 2015 6:20 AM (in response to samalaraj72)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.