Jetty endpoint exposed on port 80, not 8181

[ksimpson]

Scenario:

     - Deployed bundle with Camel route on remote VM

     - Camel route begins with a 'from("jetty:http://remoteVMName/foo/FooService")'

     - etc/system.properties contains property org.osgi.service.http.port=8181

     - etc/jetty.xml also points to port 8181

Trying to access deployed Jetty endpoint via SOAPUI on port 8181 fails, but succeeds on port 80 or without specifying port.  Where is the Fuse configuration that exposes Jetty on port 80?!  Need to know exact port so as to configure iptables properly.

Thanks,

Kevan

[ffang]

Hi,

You use

from("jetty:http://remoteVMName/foo/FooService")

here, which means a standalone jetty server port, but not the http-osgi sevice(8181), and the default port for

jetty:http://remoteVMName/foo/FooService

is 80, as you didn't specify the port in URL

Freeman

[ksimpson]

This is running in JBoss Fuse on RHEL6...  When run on Windows JBFuse, the service/route is available on port 8181; not sure I've ever tried to connect to port 80 when JBFuse is running on Windows... simply never occurred to me.

From your answer, am I to infer that JBFuse has a standalone Jetty server in addition to the Camel Jetty component?  And/or that by not specifying a port explicitly, Jetty defaults to its standard port and ignores the configuration in etc/system.properties?

UPDATE:  After deploying again on Windows without port specified, it connects on port 80 as you described.  I think some of the example Camel routes I've seen used 8181, must of gotten stuck in my head...  Thanks Freeman!