Choose to start server (no matter which one) during installation and check "Launch browser after server startup" option. Browser is not launched after server startup.
I've have tested the browser launch option in Winodws 7, Fedora 18 and, RHEL 6.4. In all cases the browser was launched once the installation was complete. Could you please provide more detail. Thanks you.
Hi Miles, I tested it now and this issue was presented only in ER1. It is working with ER3 so it seem that this was accidentally fixed :). Sorry for inconvenience, I'll put exact affected version to all BZs in future to avoid these confusions. Closing as verified. Verified on EAP 6.2.0.ER3
This is back with EAP 6.2.0.ER4. Reproduce it with standalone (domain is buggy BZ1015573). I am also missing "Application Server successfully started." string once the server is ready. (adding blocker flag as this is a regression against 6.1.1)
I've created a new BZ for missing "Application Server successfully started." string (see BZ1016639).
Petr, I'm not sure if we should retain this feature for future releases, unless there's a specific ERD requirement for it. FSW has removed the feature for its installer, because it causes issues and is probably not a very valuable feature. I'd like to open up the option of simply removing this feature going forward. What do you think?
I agree with Thom's note above: It doesn't seem like this is a useful feature. Also, it becomes difficult for the user to shut the server down afterwards since it's not launched from within a console, and specially if something goes wrong and the admin interface isn't up. That said, I've restored the browser startup feature: http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=99b1c889981a944d3551876d83b01627adb3de12 And also re-added the "Application Server successfully Started" string, along with a shutdown string for when server is brought down during post-install: http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=b9252587656e0fd24ccf8b5077207c7ba3b2fa12
I also agree as hunting zombie processes once server fail to start is making this feature quite user unfriendly. We'd get rid also of BZ982191 once we remove this.
Verified on EAP 6.2.0.ER6.