Hi Florent,
If you add org.osgi.service.http.enabled=false to the etc/system.properties, that should be the trigger for Pax Web to avoid starting the default HTTP service. You will probably also have to remove/rename the etc/jetty.xml file to avoid the Jetty connector being started anyway when applying the custom configuration. Regards, Gert Vanthienen On Fri, Dec 19, 2014 at 10:48 AM, Florent Angebault <[email protected]> wrote: > A customer is willing to disable unused listening sockets on their > servers for security reasons. > Since they don't make use of the WebConsole they would like to prevent > ServiceMix from listening on port 8181. > > Since I'm not familiar with ServiceMix I suggested to restrict jetty to > listening only on loopback device by editing jetty.xml. But I couldn't > find a way to totally prevent jetty from starting. > > After that, I tried to uninstall the jetty feature using karaf but it > seems to cause a lot of trouble: I also had to uninstall many other > features depending on it. > It doesn't seem to be a good approach. > > Is there a better solution? > > -- > Florent Angebault
