Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <207876249.1253517171977.JavaMail.jira@brutus>
Date: Mon, 21 Sep 2009 00:12:51 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Reopened: (CAMEL-1800) EventDrivenConsumer - Wait starting
 them until all other processors / routes have been started
In-Reply-To: <949416980.1246856647681.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reopened CAMEL-1800:
--------------------------------


> EventDrivenConsumer - Wait starting them until all other processors / routes have been started
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1800
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1800
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0-M2
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>
> We should wait starting the *input* to the CamelContext until all child processors and other services have been started.
> Then at the end we should _open the gates_ by starting all the input consumers.
> That should also help unit testing on slower boxes where these consumers might start a bit early and the remaining work starting the other processors is slow and thus the consumer is too fast.

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