Hi Harald, it's probably due to the "default" connector started by pax web.
You have to provide/update the port in etc/org.ops4j.pax.web.cfg (in addition of the etc/jetty.xml).
Regards JB On 05/30/2014 03:11 PM, harald wrote:
Hello list, I'm a little bit confused. To prepare a demo I installed SMX 5.0.1 into two separate folders on the same machine. SMX-A should use port range 10xxx and SMX-B should use 20xxx. To prepare the SMX-A instance I edited some files within the etc folder. To define a different Jetty port I modified org.ops4j.pax.web.cfg.empty.stub and system.properties. Than I started the SMX-A instance for the first time to let SMX create the activemq.xml and the jetty.xml. Updated these files as well and started SMX-A again. Within the logs I see: 14:06:09,726 | INFO | b Runtime worker | JettyServerImpl | 133 - org.ops4j.pax.web.pax-web-jetty - 1.1.17 | Pax Web available at [0.0.0.0]:[10080] 14:06:09,729 | INFO | b Runtime worker | JettyServerImpl | 133 - org.ops4j.pax.web.pax-web-jetty - 1.1.17 | Pax Web available at [0.0.0.0]:[8181] Is there any easy explanation why jetty is still listening on port 8181?? And maybe .. is there an easy way of redefining the port completely? For curiosity I prepared SMX-B as well and used the proper port range. It's only complaining about the jetty setup with the expected message: Caused by: java.net.BindException: Address already in use Thanks for any hint! harald -- View this message in context: http://servicemix.396122.n5.nabble.com/Two-local-smx-installations-jetty-port-tp5720569.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
