Jetty continuation timeout ignored in Karaf

Hello all,

I am experimenting with Camel (2.13.2) routes using Karaf (2.3.7) as the
runtime. I encountered a problem with Jetty continuation timeouts. They seem
to get ignored. It does not matter whether I explicitly set the timeout or
leave the default. During deployment of the bundle containing the route I
get different log output, but in neither case does the timeout fire.

Endpoint with default for continuation timeout:
<camel:endpoint id="jetty.http.server"
uri="jetty:http://0.0.0.0:1978/my/frontend?disableStreamCache=true" />

Karaf log:
2014-09-18 11:04:04,799 | INFO | ExtenderThread-2 | JettyHttpComponent
| mponent.jetty.JettyHttpComponent 946 | 102 - org.apache.camel.camel-jetty
- 2.13.2 | Using default Jetty continuation timeout for:
Endpoint[http://0.0.0.0:1978/my/frontend?disableStreamCache=true]

Endpoint with continuation timeout set to 1s:
<camel:endpoint id="jetty.http.server"
uri="jetty:http://0.0.0.0:1978/my/frontend?disableStreamCache=true橪;continuationTimeout=1000"
/>

Karaf log:
2014-09-18 14:05:00,895 | INFO | ExtenderThread-2 | JettyHttpComponent
| mponent.jetty.JettyHttpComponent 943 | 102 - org.apache.camel.camel-jetty
- 2.13.2 | Using Jetty continuation timeout: 1000 millis for:
Endpoint[http://0.0.0.0:1978/my/frontend?disableStreamCache=true]

My $KARAF_HOME/etc/jetty.xml is lock stock and does not contain a connector
configuration for port 1978.

I am testing this by POSTing a file to the route with curl, then inspecting
the file with a bean in the route. In the bean I set a breakpoint and just
wait. Outside Karaf the client is returned an error after the continuation
timeout period and the timeout is logged by Camel. Doing this in Karaf just
waits "forever".

Is this expected behavior? If it is, why?

Thanks!
Ralf