Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C6A5F3ED for ; Wed, 10 Apr 2013 21:21:17 +0000 (UTC) Received: (qmail 1226 invoked by uid 500); 10 Apr 2013 21:21:16 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 1175 invoked by uid 500); 10 Apr 2013 21:21:16 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 1113 invoked by uid 99); 10 Apr 2013 21:21:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Apr 2013 21:21:16 +0000 Date: Wed, 10 Apr 2013 21:21:16 +0000 (UTC) From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CAMEL-6259) Scheduled thread pools is not removed from JMX when shutting down MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-6259?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian M=C3=BCller closed CAMEL-6259. ----------------------------------- Resolution: Fixed Because we redo the Camel 2.11.0 release, this issue in now included in Cam= el 2.11.0 =20 > Scheduled thread pools is not removed from JMX when shutting down > ----------------------------------------------------------------- > > Key: CAMEL-6259 > URL: https://issues.apache.org/jira/browse/CAMEL-6259 > Project: Camel > Issue Type: Bug > Components: camel-core, jmx > Affects Versions: 2.10.4 > Reporter: Claus Ibsen > Assignee: Claus Ibsen > Fix For: 2.10.5, 2.11.0 > > Attachments: pools.png > > > For example if a route use the aggragate eip with a completion timeout, t= hen the scheduled thread pool is enlisted in JMX. But not removed when the = route is removed. Though as fail-safe we always remove the JMX when camel i= s stopping. > But for people doing dynamic add/remove routes this can become a problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira