Christoph Läubrich created CAMEL-9635:
-----------------------------------------
Summary: Continuation settings are only evaluated on first
creation for each port/connector
Key: CAMEL-9635
URL: https://issues.apache.org/jira/browse/CAMEL-9635
Project: Camel
Issue Type: Bug
Components: camel-jetty
Affects Versions: 2.16.2, 2.15.5, 2.16.1, 2.15.4, 2.14.4, 2.16.0, 2.15.3,
2.15.2, 2.15.1, 2.15.0, 2.14.3, 2.14.2, 2.14.1, 2.14.0, 2.13.4, 2.13.3, 2.13.2,
2.13.1, 2.13.0, 2.12.5, 2.12.4, 2.12.3, 2.12.2, 2.12.1, 2.12.0, 2.11.4, 2.11.3,
2.11.2, 2.11.1, 2.11.0, 2.10.7, 2.10.6, 2.10.5, 2.10.4, 2.10.3, 2.10.2, 2.10.1,
2.10.0
Reporter: Christoph Läubrich
Assume the following endpoints configured (in this order!):
{code}<from uri="jetty:http://0.0.0.0/myservice1/?useContinuation=false"/>
<from uri="jetty:http://0.0.0.0/myservice2/?useContinuation=true"/>
<from uri="jetty:http://0.0.0.0:9090/myservice3/"/>
<from
uri="jetty:http://0.0.0.0:9090/myservice4/?continuationTimeout=10000"/>{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
