Created attachment 705437 [details] Standalone console output According to documentation we should be able to use re-use EAP configurations from older versions just by copy the EAP_HOME/domain/ and EAP_HOME/standalone/ directories from the previous installation over the new installation directories, but I am unable to start EAP6.1 with configuration files from EAP6.0.1 or EAP6.0.0. try: unzip -q jboss-eap-6.1.0.ER1.zip unzip jboss-eap-6.0.1.zip jboss-eap-6.0/standalone/* unzip jboss-eap-6.0.1.zip jboss-eap-6.0/domain/* cp -r jboss-eap-6.0/standalone/* jboss-eap-6.1/standalone/ cp -r jboss-eap-6.0/domain/* jboss-eap-6.1/domain/ calling ./jboss-eap-6.1/bin/standalone.sh will not start server and ./jboss-eap-6.1/bin/domain.sh will start it with exceptions (see attachments). There is workaround for standalone. Just copy configuration files to external folder and add -Djboss.server.config.dir argument. mkdir config JBOSS_CONFIG_DIR=`pwd`/config mv jboss-eap-6.1/standalone/configuration/* config/ ./jboss-eap-6.1/bin/standalone.sh -Djboss.server.config.dir=$JBOSS_CONFIG_DIR Server will start with just one exception (see BZ 918030) stop server and return configuration files back ./jboss-eap-6.1/bin/jboss-cli.sh -c command=:shutdown mv config/* jboss-eap-6.1/standalone/configuration/ ./jboss-eap-6.1/bin/standalone.sh now will server starts without any exception
Created attachment 705438 [details] Domain console output
This is due to a mismatch of the class types of the file handler. The logging.properties has a handler called FILE that's a org.jboss.logmanager.handlers.FileHandler. The xxx.xml has a handler called FILE that's a org.jboss.logmanager.handlers.PeriodicRotatingFileHandler. When the operations are processed only the handler name is checked which results in the error as a FileHandler doesn't have the same properties as a PeriodicRotatingFileHandler. There is an upstream fix that has been merged to solve this mismatched type issue that will fix this too. https://github.com/jbossas/jboss-as/commit/2f16ce07fcad89a9047ecd131869034901522ef6 I'll do a PR for EAP too.
Verified on EAP 6.1.0 ER3, using configurations from older EAP is now working.
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html