mike just wrote:
Do you mean adding one -Djboss.socket.binding.port-offset=100 to both of them like
standalone.bat --server-config=standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
standalone.bat --server-config=standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
or something else?
No, with a virtual IP address you need to change the configuration that your NIC accept the 'real' IP address and additional some 'virtual' IP's.
That mean JBoss can run at IP *.1 AND *.2 which are handled as different addresses and you can select it by IP from foreign hosts instead of using port-offset.
If you can not change the configuration you need to use port-offset and start one instance with a different offset
standalone.bat --server-config=standalone-full-ha.xml
standalone.bat --server-config=standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
In this case you can reach the instance via browser with 8080/9990 and the second with 8180/10099
Thanks. That makes it work by adding one more parameter "-Djboss.node.name=node2". Thanks for your help.
<inet-address value="${jboss.bind.address:0.0.0.0}"/>
I wouldn't bind to all interfaces. I would always recommend binding to one.
Do you mean adding one -Djboss.socket.binding.port-offset=100 to both of them like
standalone.bat --server-config=standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
standalone.bat --server-config=standalone-full-ha.xml -Djboss.socket.binding.port-offset=100
or something else?
Only add that parameter to one of the servers, thus one will listen on 8080 and another one 8180. Only one process can listen on one port.