Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D32DA200C69 for ; Sat, 6 May 2017 14:34:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D1D99160BAD; Sat, 6 May 2017 12:34:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 244A0160BA2 for ; Sat, 6 May 2017 14:34:28 +0200 (CEST) Received: (qmail 87925 invoked by uid 500); 6 May 2017 12:34:28 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 87913 invoked by uid 99); 6 May 2017 12:34:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 May 2017 12:34:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 92078C108E for ; Sat, 6 May 2017 12:34:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id tG31GvyXVIFX for ; Sat, 6 May 2017 12:34:27 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CAFEF5F1BA for ; Sat, 6 May 2017 12:34:26 +0000 (UTC) Received: from static.162.255.23.22.macminivault.com (unknown [162.255.23.22]) by mwork.nabble.com (Postfix) with ESMTP id 933CF3F74E3E2 for ; Sat, 6 May 2017 05:34:25 -0700 (MST) Date: Sat, 6 May 2017 05:34:25 -0700 (MST) From: Hetmoteus To: users@camel.apache.org Message-ID: <1494074065597-5798802.post@n5.nabble.com> Subject: OnApplicationEvent not called with CamelAutoConfiguration MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Sat, 06 May 2017 12:34:30 -0000 Hi, I'm using SpringBoot with camel 1.4.3.RELEASE 2.18.3 CamelContext is auto configured via : CamelAutoConfiguration If I understand correctly the SpringCamelContext is instancied via CamelAutoConfiguration class and not by CamelContextFactoryBean. Since https://issues.apache.org/jira/browse/CAMEL-2607, the SpringCamelContext doesn't implement ApplicationListener interface anymore. It seems like onApplicationEvent is not called on the SpringCamelContext which in my situation cause the AMQ ConnectionFactory to be destroyed before the camel graceful shutdown. Anyone has this issue or can confirm ? Has a fix, I created a component which is listening ApplicationEvent and forwarding them to injected SpringCamelContext. Thanks -- View this message in context: http://camel.465427.n5.nabble.com/OnApplicationEvent-not-called-with-CamelAutoConfiguration-tp5798802.html Sent from the Camel - Users mailing list archive at Nabble.com.