camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2811) CamelContexts seems to not correctly create their own instance of an imported routeContext.
Date Wed, 16 Jun 2010 08:18:52 GMT

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

Willem Jiang commented on CAMEL-2811:
-------------------------------------

Yes, you need to build the camel trunk from scratch. 

> CamelContexts seems to not correctly create their own instance of an imported routeContext.
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2811
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2811
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.3.0
>            Reporter: Andreas Asmuss
>            Assignee: Willem Jiang
>             Fix For: 2.4.0
>
>         Attachments: RouteContextInstanceError.zip
>
>
> Issue: http://old.nabble.com/Direct-route-not-shared-across-contexts--td28766143.html
> When two CamelContexts import the same routeContext they should instantiate their own
route based on the definition in the routeContext. But something is not working correctly.
One example is having a directqueue of the same name in each route-instance. Camel crashed
with the exception:
> org.apache.camel.RuntimeCamelException: java.lang.IllegalStateException: Endpoint direct://foo
only allows 1 active consumer but you attempted to start a 2nd consumer.
> 	at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1126)
> 	at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:103)
...
> This is demonstrated in the sample file attached to this issue.
> Obviously this makes other things than the direct-endpoints malfunction. But this should
be enough to show the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message