Hide Forgot
Description of problem: User can enter value for osgi-http port number during Socket Binding configuration for all profiles both standalone and domain. But this port is never used by EAP. Version-Release number of selected component (if applicable): EAP 6.2.0.CR3 How reproducible: Always Steps to Reproduce: 1. Run the gui installation. Go to socket bindings screen using default values. 2. Choose to configure custom port bindings and choose at lease one of server modes, and pres Next. Actual results: Notice that there is osgi-http port number item (unless you are on domain-host screen) with default port 8090, but this is never used by EAP. Expected results: Remove osgi-http property from EAP installer at all.
Removed osgi-http property from the EAP installer. http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=c5859da9d6637d647b682a18d445706aec459f1c
This is fixed in EAP 6.3.0.ER1. Please move all relevant BZs to ON_QA so I can verify them.
Verified on EAP 6.3.0.ER2