Description of problem: Port offset modifier is doubled to the value selected by user. Version-Release number of selected component (if applicable): EAP 6.2.0.CR3 How reproducible: Always Steps to Reproduce: 1. Start the gui installation, go to Socket Binding screen using default values. 2. Select to "Configure an offset for all default port bindings". 3. Select "+100 offset" option (you can choose arbitrary value, result will be the same) 4. Finish the installation. Go to $JBOSS_HOME/domain/configuration/ and observer host files. Actual results: Port offset 200 is used for most of values in host.xml files. Expected results: Port offset 100 is used as selected by user. Additional info: host.xml - management native port offset is doubled - management http port offset is doubled - server offsets are fine host-master.xml - management native port offset is doubled - management http port offset is doubled host-slave.xml - management native port offset is doubled - domain master port is fine - server offsets are missing (covered by BZ1034057)
Ports will not longer be doubled by offset. http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=439c5e594ba2d0dbd1004a2617aa6419e704a6c1
This is still a velid issue for EAP 6.3.0.ER1 installer. - set automatic port offset to +1 - open jboss-eap-6.3/domain/configuration/host.xml file Actual <management-interfaces> <native-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.native.port:10001}"/> </native-interface> <http-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.http.port:9992}"/> </http-interface> </management-interfaces> Expected <management-interfaces> <native-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.native.port:10000}"/> </native-interface> <http-interface security-realm="ManagementRealm"> <socket interface="management" port="${jboss.management.http.port:9991}"/> </http-interface> </management-interfaces>
This has been resolved in ER2.
Verified on EAP 6.3.0.ER2 installer.
Changed <guilabel></guilabel> tag in Doc Text to ticks (`) to fix Bug 1096865
marking for exclusion from release notes as per bug 1097065.
Re-adding the doc_text flag as it was removed due to beta RN.