Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-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 EA847182E6 for ; Mon, 20 Jul 2015 15:34:04 +0000 (UTC) Received: (qmail 9562 invoked by uid 500); 20 Jul 2015 15:34:04 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 9536 invoked by uid 500); 20 Jul 2015 15:34:04 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 9463 invoked by uid 99); 20 Jul 2015 15:34:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jul 2015 15:34:04 +0000 Date: Mon, 20 Jul 2015 15:34:04 +0000 (UTC) From: "Stuart McCulloch (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-3864) Warning when shutting down system with karaf-cellar installed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart McCulloch updated KARAF-3864: ------------------------------------ Summary: Warning when shutting down system with karaf-cellar installed (was: Exception logged when shutting down system with karaf-cellar installed) > Warning when shutting down system with karaf-cellar installed > ------------------------------------------------------------- > > Key: KARAF-3864 > URL: https://issues.apache.org/jira/browse/KARAF-3864 > Project: Karaf > Issue Type: Bug > Components: cellar-bundle > Reporter: Stuart McCulloch > > We're experimenting with karaf-cellar 3.0.3 on top of karaf 3.0.4 and get the following exception if the system is forcibly stopped: > {code} > 2015-07-20 16:19:03,397+0100 WARN [FelixShutdown] org.apache.karaf.cellar.bundle.LocalBundleListener - CELLAR BUNDLE: can't check listener configuration > org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed: (objectClass=org.osgi.service.cm.ConfigurationAdmin) > at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:240) [org.apache.aries.blueprint.core:1.4.3] > at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:55) [org.apache.aries.blueprint.core:1.4.3] > at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:298) [org.apache.aries.blueprint.core:1.4.3] > at Proxy90cff4fa_9fee_4d56_85e6_c006a413befa.getConfiguration(Unknown Source) [na:na] > at org.apache.karaf.cellar.bundle.LocalBundleListener.isEnabled(LocalBundleListener.java:150) [org.apache.karaf.cellar.bundle:3.0.4.SNAPSHOT] > at org.apache.karaf.cellar.bundle.LocalBundleListener.bundleChanged(LocalBundleListener.java:51) [org.apache.karaf.cellar.bundle:3.0.4.SNAPSHOT] > at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:868) [org.apache.felix.framework-4.2.1.jar:na] > at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789) [org.apache.felix.framework-4.2.1.jar:na] > at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514) [org.apache.felix.framework-4.2.1.jar:na] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403) [org.apache.felix.framework-4.2.1.jar:na] > at org.apache.felix.framework.Felix.stopBundle(Felix.java:2520) [org.apache.felix.framework-4.2.1.jar:na] > at org.apache.felix.framework.Felix$2.run(Felix.java:959) [org.apache.felix.framework-4.2.1.jar:na] > at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80] > {code} > Looking at the LocalBundleListener code it checks if the listener is enabled before going on to check whether the system is shutting down. However the "isEnabled" check uses the blueprint-injected ConfigurationAdmin service which is not available during shutdown. Swapping these checks round fixes the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)