[
https://issues.apache.org/jira/browse/CAMEL-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved CAMEL-9311.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.15.5)
Fixed in
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commit;h=8a770bfeec6e2134eec12be6ef49a3458e99f7cc
for {{master}}
and in
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=commit;h=59b54c67909f215fd41bb0ee3ba66a8968195563
for {{camel-2.16.x}}
> Concurrency issue with the dynamic router
> -----------------------------------------
>
> Key: CAMEL-9311
> URL: https://issues.apache.org/jira/browse/CAMEL-9311
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.15.1
> Reporter: Joe Luo
> Assignee: Gert Vanthienen
> Fix For: 2.16.1, 2.17.0
>
> Attachments: dynamicRouterConcurrentTest.zip
>
>
> We have a service with two HTTP contexts:
> http://0.0.0.0:9000/endpoin1/dynamic";
> http://0.0.0.0:9000/endpoin2/dynamic";
> Both endpoints can be called using a HTTP GET method and a dynamic router
> routes the message differently.
> Each HTTP endpoint has its own instance of the dynamic router bean. The
> dynamic router bean does not use any shared state.
> When the HTTP endpoints are called sequentially the calls are handled as
> expected. When the HTTP endpoints are called concurrently then sometimes the
> the dynamic router of the 9000/endpoin1/dynamic endpoint is re-routing calls
> originating from 9000/endpoin2/dynamic and vice versa.
> Please take a look at attached unit test case for more detail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
