Assume the following endpoints configured (in this order!):
This results in endpoints myservice1 and myservice2 NOT using continuation, and myservice4 usind the default timeout of 30seconds.
This is especially confusing if you use something like bluprint where different bundles might use the jetty endpoint with different configurations. In such a case it is highly dependant on the start order what configuration wins that makes this issue more confusing and hard to debug.
The cause of this is, that the configuration of the endpoint is only evaluated once when the Connector is created and then never changed as long as you do not shut down ALL endpoints of this connector.
This can be fixed by reading the configuration on each request instead of once at connector creation.
I have seen this issue on Camel 2.10 but the code seems not to have changed in the master until now, so I'll provide a patch for the master branch only.