[
https://issues.apache.org/jira/browse/CAMEL-10525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695766#comment-15695766
]
Claus Ibsen commented on CAMEL-10525:
-------------------------------------
This is not a bug, you should not add the same route instance to two different
camel contexts.
> AggregationController is not CamelContext-Aware
> -----------------------------------------------
>
> Key: CAMEL-10525
> URL: https://issues.apache.org/jira/browse/CAMEL-10525
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.18.0
> Reporter: Stefan
> Labels: aggregator
> Attachments: AggregationControllerMultiContextTest.zip
>
>
> I have a route definition using an AggregationController. If this this route
> definition is added to multiple CamelContexts, I end up with two
> AggregateProcessors (one for each context) pointing to the same
> AggregationController pointing to the AggregateProcessor in the last started
> CamelContext.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
