Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-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 12CA5106FE for ; Fri, 8 Aug 2014 16:59:18 +0000 (UTC) Received: (qmail 82039 invoked by uid 500); 8 Aug 2014 16:59:12 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 81976 invoked by uid 500); 8 Aug 2014 16:59:12 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 81919 invoked by uid 99); 8 Aug 2014 16:59:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Aug 2014 16:59:12 +0000 Date: Fri, 8 Aug 2014 16:59:12 +0000 (UTC) From: "Heath Kesler (JIRA)" To: dev@aries.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARIES-1233) Stale service reference retention on consumer bundle after service provider bundle update. 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/ARIES-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090964#comment-14090964 ] Heath Kesler commented on ARIES-1233: ------------------------------------- I believe this ticket can be closed, I believe it was an implementation issue. The issue was that a single bean from bundle A was being initialized in spring and exposed in 2 different service with 2 different interfaces. if you initialize a separate bean for each service the problem goes away. > Stale service reference retention on consumer bundle after service provider bundle update. > ------------------------------------------------------------------------------------------ > > Key: ARIES-1233 > URL: https://issues.apache.org/jira/browse/ARIES-1233 > Project: Aries > Issue Type: Bug > Components: Blueprint > Environment: Apache Karaf 3.0.1 > Reporter: Jamie goodyear > > Three Bundles, A, B, and C. > Bundle A provides a service, which is wired via BP. > Bundles B and C consume the service via BP references. Service trackers are enabled, showing that both bundles are aware of when the service provider updates. > Bundle A configuration property tells the service to use bundle B or C for processing. Upon a configuration update the consuming bundles B and C will contain stale references to the Bundle A service. Refreshing/Restarting their bundles will correct the wiring. The BP container should refresh these service references automatically. > I'm working on a stripped down demonstration test case to illustrate the issue. -- This message was sent by Atlassian JIRA (v6.2#6252)