Return-Path: X-Original-To: apmail-felix-dev-archive@www.apache.org Delivered-To: apmail-felix-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 696EE18351 for ; Thu, 25 Feb 2016 16:23:20 +0000 (UTC) Received: (qmail 94155 invoked by uid 500); 25 Feb 2016 16:23:18 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 94032 invoked by uid 500); 25 Feb 2016 16:23:18 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 93680 invoked by uid 99); 25 Feb 2016 16:23:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Feb 2016 16:23:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 258E82C1F5D for ; Thu, 25 Feb 2016 16:23:18 +0000 (UTC) Date: Thu, 25 Feb 2016 16:23:18 +0000 (UTC) From: "David Bosschaert (JIRA)" To: dev@felix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FELIX-5198) Service should not be available while being unregistered 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/FELIX-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated FELIX-5198: ------------------------------------ Attachment: (was: felix-5198.patch) > Service should not be available while being unregistered > -------------------------------------------------------- > > Key: FELIX-5198 > URL: https://issues.apache.org/jira/browse/FELIX-5198 > Project: Felix > Issue Type: Bug > Components: Framework > Affects Versions: framework-5.4.0 > Reporter: Carsten Ziegeler > Assignee: David Bosschaert > Fix For: framework-5.6.0 > > Attachments: felix-5198.patch > > > Currently it is possible to get a service while it is being unregistered - if the service is get during processing of the unregistering event. This is the order of events: > a) a service (factory) is unregistered in the framework > b) the UNREGISTERING event is sent before the service is actually unregistered (this is as defined in the spec) > c) the above event is handled synchronously, reactivating dependent components > d) during this reactivation, some component looks up the service that is unregistered in a). as this service is still registered and marked as valid, it gets it > According to ServiceRegistration.unregister the service should not be available anymore while the events are sent -- This message was sent by Atlassian JIRA (v6.3.4#6332)