Steps to Reproduce: 1. Run soa installer, fill in all necessary fields 2. On the Post-Install installer step quit the installation 3. Re-run soa installer 4. User cannot reinstall to the same eap folder as in step 1. EAP is malformed. Expected results: User can re-install.
Let's have these scenarios: a) * install soa using the installer - (success) * re-run the installer (select the same install folder), finish installation. (success) b) * install soa using the installer, on the very last page ('Creating Shortcuts') hit on quit and confirm. (success) * re-run the installer (select the same install folder), hit 'next'. Now there is an error dialog saying: product.conf file is either malformed or does not exist. (fail) User should be able to reinstall soa in scenario b).
The installer now backs up files that will be modified. Current list is: $JBOSS_HOME/bin/product.conf $JBOSS_HOME/modules/layers.conf $JBOSS_HOME/standalone/configuration/standalone*.xml $JBOSS_HOME/domain/configuration/domain.xml $JBOSS_HOME/domain/configuration/host.xml If the installation is cancelled early, the new files are deleted and the backups restored. If it is not, the backups are deleted upon installer completion. Relevant commit: d07fd58ac39f38c5db4766086f04abeaebad38bd
Created attachment 799227 [details] screen-2
I still hit the issue: a) after hitting on quit I cannot start EAP anymore b) after hittin on quit I cannot reinstall soa to the same folder
Error: missing product.conf file
This was fixed, but some changes in IzPack unfortunately destroyed the functionality. It cannot be put into beta, but will be available for builds after that.
Verified in ER4 build.
Steps to Reproduce: 1. Run soa installer, fill in all necessary fields 2. On the Post-Install installer step quit the installation 3. Re-run soa installer 4. User cannot reinstall to the same eap folder as in step 1. EAP is malformed. (see attachment)
Hello Tomas, I'm having trouble reproducing this issue. I'll continue trying today but none of f my attempts result in malformed EAP; some do, however, result in failed installs.
Created attachment 848217 [details] Processing page Hello Thomas, I'm quitting the installation during "processing" (see attachment). Re-run SOA installer ends with described error.
The backup / restoration process has been modified to backup the user's entire EAP installation. This will then either be discarded or put back upon installer failure / cancellation.
I still see some problems. If I attempt to quit the installation during "processing" on step 13, then there is java process not terminated properly on installer finish which prevents user to re-run the installation unless he 'pkill java' in terminal. `ps ax | grep java` gives: 21365 pts/0 Sl 0:03 /usr/lib/jvm/java-7-oracle/bin/java -D[Standalone] -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djava.security.manager -Djava.security.policy=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/bin/security.policy -Drtgov.security.policy=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/bin/rtgov.policy -Dorg.jboss.boot.log.file=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone/log/server.log -Dlogging.configuration=file:/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone/configuration/logging.properties -jar /home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/jboss-modules.jar -mp /home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1 -Djboss.server.base.dir=/home/psrna/data/soa/tests/soa-installer.test/eap61/jboss-eap-6.1/standalone --admin-only --server-config=standalone.xml
Hi Pavol, I am having trouble reproducing the problem described in your last comment (16). Is this something you can reproduce every try, or only happens intermittently? Is there a particular job during the "processing" step where you quit to reproduce this error? thanks.
Please disregard my previous comment. I was able to reproduce this error by quitting the installation during processing precisely after the command to start up the server is first sent, but before the server has had time to display it's started code. I've modified the Installer to track this intermediate 'starting' state, and to run the shutdown command during cleanup if the server was in this state when the user quit. See commit: http://git.app.eng.bos.redhat.com/installer-commons.git/commit/?h=6.1.1.ip&id=970b84c47f7e5afc709659332d03af9dcf0ab429
Hi Pavol, Can you give a bit more info on how to reproduce this issue? Which job number is the processing panel at when you hit quit? Or perhaps attach the InstallationLog.txt file. Also, some info about your OS and environment. thanks!
Hi Francisco, the trick is to quit the installation in the right step. If I hit on quit during the postinstallation phase in step 14/110 then the java process is not terminated. I recently tried on RHEL6 and openJDK7.
Created attachment 854377 [details] InstallationLog.txt
The installer now backs up the entire jboss-eap-6.1 directory that already existed on the user's system, and restores that after pressing the quit button.