Issue

• In a standalone Fuse installation, the usualf way to change the Pax-Web port (used by the Hawtio console, among other things) is to edit the files etc/jetty.xml and etc/org.ops4j.pax.web.cfg. These changes have no effect in a fabric environment, even though the files may exist for a specific container. In fact, the container may overwrite the changes made by editing these files.

• How to change http port for the second node in the fabric ?

• Child container port http changes are rolled back automatically

• How to enable custom port for webservice on child Container ? We have parent container and child container , we set default ports 8107 on parent port in jetty.xml and 8108 port on child container. Webservice deployed on parent port are working and webservice on child port 8108 is not working For example http://XYZ:807/cxf is working and http://XYZ:8108/cxf is not working. XYZ is the parent container name.

• This is for better understanding of the way Fuse assigns ports.

• After Fuse service restart the HTTP port of Fabric view is getting changed. We tried with some possible ports like 8181,8182,8183 and 8184 but still we got not able to open in browser. As we are in clustered environment we are performing deployments from other server but some time we are experiencing the same in all three servers.