I have problem with long running requests - they timeout.
They are serviced by default connector,
how can I change it's timeout?
I tried adding connector to etc/jetty.xml
<Set name="host"><Property name="jetty.host" /></Set>
It was added to the default connector, but later my requests are serviced by the default connector with timeout 200.000 instead of by my connector.
How can I prevent default connector from being created or configure it's timeout?
(it seems to me that changing it's timeout is impossible, I also can't prevent it from being created and added)
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
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//
DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd">
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.
So what you should have is
<Set name="port"><Property name="jetty.port" default="8181"/></Set>
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.