Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 918103

Summary: Unable to use configuration files from older versions of EAP
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Kremensky <pkremens>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: brian.stansberry, jperkins, smcgowan
Target Milestone: ER3   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Standalone console output
none
Domain console output none

Description Petr Kremensky 2013-03-05 13:40:42 UTC 
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
Comment 1 Petr Kremensky 2013-03-05 13:41:12 UTC 
Created attachment 705438 [details]
Domain console output
Comment 2 James Perkins 2013-03-05 16:44:24 UTC 
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.
Comment 4 Petr Kremensky 2013-03-21 08:30:01 UTC 
Verified on EAP 6.1.0 ER3, using configurations from older EAP is now working.
Comment 7 mark yarborough 2013-07-23 18:44:56 UTC 
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html