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 (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/18 10:01:42 UTC
[jira] [Resolved] (CAMEL-4912) Starting CamelContext should start
routes after the CamelContext state has been set to started
[ https://issues.apache.org/jira/browse/CAMEL-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4912.
--------------------------------
Resolution: Won't Fix
Starting routes while CamelContext is starting has been baked in, to rely on this fact, as it help ensure JMX stuff is setup correctly as well.
> Starting CamelContext should start routes after the CamelContext state has been set to started
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-4912
> URL: https://issues.apache.org/jira/browse/CAMEL-4912
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.10.0
>
>
> When routes are started, they may poll and and intake new messages, that gets routed in the Camel routes.
> So its best that the CamelContext state has been changed from starting to started. To indicate the CamelContext has been fully started.
> Otherwise you may have a odd race condition, that you process a new message, while the state of CamelContext is starting.
> For example as we have with the SedaConsumer that in CAMEL-4911
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira