Red Hat Bugzilla – Bug 1007791
Installer: Port offset configure only standalone profiles
Last modified: 2017-10-09 20:07:41 EDT
On Socket binding screen choose to configure an offset for all default port bindings, choose some port offset and finish the installation.
Only standalone profiles have port offset configured.
There will be port offset configured also for domain profiles.
Did some digging with this one.
The installer currently modifies the port-offset attribute in jboss-eap-6.2/domain/configuration/host.xml. Here is the snippet:
As you can see, the installer currently changes the port-offset to server-one..but not server-two nor server-three. We have a few options:
a) Add the offset to the rest of the host.xml servers. This would just mean having the installer do a simple addition of the given value (the user gives X as the offset amount, then server-one will be offset by X, server-two by X+150, and server-three by X+250.
b) Add the offset directly to domain.xml in the relevant <socket-binding-group> element.
This is a tricky decision.
As there is nothing like <socket-binding-group/> for domain.xml, options you listed are IMO the only ones we have.
I don't really like the idea of hard-coding the offset directly to each port inside domain.xml, so from my point of view the a) option is less evil, but if you prefer b) we can further discuss this.
User can always use custom port bindings to change ports inside domain.xml directly, so option a) is definitely better one.
option a) from my comment above has been added to the installer.
Verified on EAP 6.2.0.ER2