Return-Path: 
 <dev-return-39647-apmail-camel-dev-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-dev-archive@www.apache.org
Delivered-To: apmail-camel-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5A73010741
	for <apmail-camel-dev-archive@www.apache.org>;
 Fri, 28 Feb 2014 14:07:39 +0000 (UTC)
Received: (qmail 27123 invoked by uid 500); 28 Feb 2014 14:07:38 -0000
Delivered-To: apmail-camel-dev-archive@camel.apache.org
Received: (qmail 27086 invoked by uid 500); 28 Feb 2014 14:07:37 -0000
Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@camel.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@camel.apache.org>
List-Post: <mailto:dev@camel.apache.org>
List-Id: <dev.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list dev@camel.apache.org
Received: (qmail 27076 invoked by uid 99); 28 Feb 2014 14:07:37 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 14:07:37 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.213.172 as permitted sender)
Received: from [209.85.213.172] (HELO mail-ig0-f172.google.com)
 (209.85.213.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 14:07:33 +0000
Received: by mail-ig0-f172.google.com with SMTP id h3so1670658igd.5
        for <dev@camel.apache.org>; Fri, 28 Feb 2014 06:07:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=/jIn83D30LtJy2/G+N8gwcOtTpiKWdKc/QAupHojXr0=;
        b=KLcZ6s9MjzgIsJklgQzYfkUCYUo75TzgCpZnLsNWParjxAZhei47sXKqGZZ90reP5i
         kubLoELrHwFRjcAJ4F4RYvb1caRfoH/DdOIFVMe2deym3DhPv1s+utfzcrjwuQLjYGdi
         Xho9l4Fvn37HLQ6qN28OEk9FNU0o7Y9eIRRkKxfD+NyFKAQjQ0LhsU4C9lkncGHkS8Ur
         6nzwribxMQWd2E3uyjqjE/IBRDGhtbSHsxWP5miaCCmNDRAlaD5+xjXepLsIzv9lIGHk
         CEV7c+PkQwdx8vfz6tBx6//Mi2mCjNUQY4Htfs5kg2xgJW7ycaPeyhp3oZLKp8AQ5Qg3
         283Q==
X-Received: by 10.50.6.165 with SMTP id c5mr4235205iga.27.1393596432694; Fri,
 28 Feb 2014 06:07:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.147.69 with HTTP; Fri, 28 Feb 2014 06:06:52 -0800 (PST)
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 28 Feb 2014 15:06:52 +0100
Message-ID: 
 <CAGB5yN=n1M2Q5CHhkBtLwOyqS27r+AUH20+jx--_3Z2ZAAr_nA@mail.gmail.com>
Subject: [HEADS UP] - Camel spring now shutdown Camel eager (sooner)
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hi

See
https://issues.apache.org/jira/browse/CAMEL-7156

There can be situations when Camel spring apps shutdown, could cause
those spring exceptions during shutting down Camel. To remedy this the
end user would need to setup depends-on attributes between
<camelContext> and any bean that may fail.

>From Camel 2.13 onwards we shutdown Camel eager, which then ensures we
shutdown Camel cleanly and before any other <bean>s.

There is a new attribute on <camelContext> you can use to turn this
off, and use the old behavior.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io