Hide Forgot
Description of problem: Right now, if you want to spin up a second instance of JDG on a box, you will have to manually modify the ports in *.xml (standalone, standalone-ha). Please add the port-offset support to the out of the box xml Version-Release number of selected component (if applicable): JDG beta How reproducible: Try and use port offset with JDG server Steps to Reproduce: 1. Start up JDG server with -Djboss.socket.binding.port-offset=100 for example 2. Netstat the box, ports have not changed 3. Actual results: Ports have not changed from default Expected results: Ports incremented by 100 Additional info:
Tristan how is this solved?
Martin, if you check the various standalone.xml files you'll notice that the port offset of the socket-binding-group references the jboss.socket.binding.port-offset property <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> : </socket-binding-group>
I see, I checked config files that were already rewritten by my templates and this detail was not there so I missed it. Verified with ER7.