Please tell us exact FUSE ESB version you're using, that would be very helpful.
And you actually can specify port number for the connector, something like
This can set maxIdleTime for jetty listening port 8181.
This jetty.xml configuration is applicable for http-osgi service and cxf http-osgi transport which is based on http-osgi service.
I use apache-servicemix-4.4.1-fuse-01-13
karaf@root> list | grep http
karaf@root> list | grep cxf
karaf@root> list | grep osgi
I'm encountering the same problem with a <jaxws:endpoint> using a similar version of FUSE ESB (4.4.1-fuse-03-06) with the http-osgi transport (address attr is "/Service", not a full URL). I've tried configuring the maxIdleTimeout in etc/jetty.xml and specifying the proper port (8181), but on startup, the message is:
org.ops4j.pax.web.pax-web-jetty - 1.0.3 | Connection on port 8181 cannot be open. Reason: Address already in use
I suspect this config is conflicting with pax-web-jetty startup. I did some digging, and found this outdated documentation on how to use a fragment bundle to configure pax-web-jetty. Is this the correct approach for http-osgi transport on FUSE ESB 4.4.1 and, if so, is there any place I can find the defaults that are already in use for that bundle (e.g. port 8181)? I've looked in the pax-web-jetty bundle, but there's no config properties file in there.
It should be maxIdleTime but not maxIdleTimeOut.
So what you should have is
Also the message
Connection on port 8181 cannot be open. Reason: Address already in use
is harmless, your maxIdleTime configuration for default SelectChannelConnector already get picked up on port 8181.
And the fragment bundle thing you found is for old pax-web before 0.7.x IIRC, it's not applicable now.