You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/11/13 15:56:11 UTC

[jira] [Commented] (CAMEL-9311) Concurrency issue with the dynamic router

    [ https://issues.apache.org/jira/browse/CAMEL-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004071#comment-15004071 ] 

Claus Ibsen commented on CAMEL-9311:
------------------------------------

Well spotted and good fix [~gertvanthienen]. Make sure to get the fix into 2.16.x and 2.15.x branches.

> 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
>         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)