I just have a little question.
We have 1 DC for several HC (for different environment).
Previously, I upgraded DC from 6.1 to 6.2 and HC could stay at 6.1 or upgrade too to 6.2.
With EAP 6.3, HC is failing.
Here is an example of failing for HC 6.2 to DC 6.3 (both are fresh and no customized configuration has been implemented yet : only the minimum => authentication) :
========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/laurent/jboss/6.3_dev/jboss-eap-6.2 JAVA: java JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 12:42:58,994 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2 12:42:59,138 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller' [Host Controller] 12:42:59,747 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2 [Host Controller] 12:42:59,998 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 [Host Controller] 12:43:00,092 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting [Host Controller] 12:43:00,923 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.7.GA-redhat-1 [Host Controller] 12:43:00,946 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.7.GA-redhat-1 [Host Controller] 12:43:00,972 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.18.GA-redhat-1 [Host Controller] 12:43:01,056 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999 [Host Controller] 12:43:02,769 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-JBAS014893: Transforming resource [ [Host Controller] ("profile" => "default"), [Host Controller] ("subsystem" => "logging"), [Host Controller] ("periodic-rotating-file-handler" => "FILE") [Host Controller] ] for host controller 'wk01lhe' to subsystem 'logging' model version '1.3.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [JBAS014895: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [named-formatter]] [Host Controller] 12:43:02,797 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 20ms 12:43:03,118 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99 12:43:03,119 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process controller 12:43:03,120 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished; exiting
So, is that a "normal" behavior ? Must I upgrade DC and HC at the same time ? What if you have several environment (not acceptable to upgrade all environment at the same time => nonsense) ?