Description of problem: There is a problem in Server Launch screen. Select to start server in 'Standalone mode' by installer and to 'Launch browser after server startup'. After clicking on Next button NPE is thrown and installer is stuck. No exception is thrown if I choose 'Domain mode'. Exception in thread "Thread-10" java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:542) at java.util.Properties.setProperty(Properties.java:161) at com.izforge.izpack.installer.AutomatedInstallData.setVariable(AutomatedInstallData.java:231) at com.redhat.installer.action.PortDefaultReset.executeAction(PortDefaultReset.java:44) at com.izforge.izpack.installer.IzPanel.executePostValidationActions(IzPanel.java:1426) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1653) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1637) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.navigate(InstallerFrame.java:1800) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.access$100(InstallerFrame.java:1767) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler$1.run(InstallerFrame.java:1784) at java.lang.Thread.run(Thread.java:722) Version-Release number: EAP 6.2.0.ER2
I am unable to reproduce this error using http://download.lab.bos.redhat.com/devel/candidates/JBEAP/JBEAP-6.2.0.ER2/jboss-eap-6.2.0.ER2-installer.jar Please give more information regarding choices made earlier in the installation.
I tried it several times now and it isn't as easy to reproduce as I thought. I was able to get the same exception (installer stuck) as in description just clicking on 'Domain mode' radio, but I hit this twice from 30+ tries. I am lowering the severity to medium (as I am unable to hit this every time). I'll try some more examples tomorrow and will let you know.
I'll try to reproduce this with ER3.
Finally I found a reliable way to reproduce this (EAP 6.2.0.ER3). 1. Run the gui installation and navigate to Server Launch screen (use default values for all screens) 2. Use Alt+n and Alt+p shortcuts to navigate between screens. Go to next (Logging Options) screen (Alt+n), return to Socket Bindings (2x Alt+p), go again to Logging Option (2x Alt+n) ... and repeat this until you hit the NPE (I hit this always on first returning to Server launch screen from Socket Binging screen with ER3) I was able to hit this with RHEL6.4 and with Fedora 16
Alt+n and Alt+p keys here are used just for faster navigation, I can hit it also by clicking on Next/Previous buttons.
This NPE was fixed for ER5, but wasn't marked. My apologies. See commit for details: http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=c927537bb1d2c2ce450ba51c0c0f1f333f6b6d1c
Verified on EAP 6.2.0.ER5 installer.