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 0DC19EBBA for ; Fri, 14 Dec 2012 15:48:14 +0000 (UTC) Received: (qmail 86718 invoked by uid 500); 14 Dec 2012 15:48:13 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 86642 invoked by uid 500); 14 Dec 2012 15:48:13 -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 86439 invoked by uid 99); 14 Dec 2012 15:48:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 15:48:12 +0000 Date: Fri, 14 Dec 2012 15:48:12 +0000 (UTC) From: "Guillaume Nodet (JIRA)" To: dev@felix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FELIX-3824) Possible InvalidStateException thrown while unregistering bundle services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Guillaume Nodet created FELIX-3824: -------------------------------------- Summary: Possible InvalidStateException thrown while unregistering bundle services Key: FELIX-3824 URL: https://issues.apache.org/jira/browse/FELIX-3824 Project: Felix Issue Type: Bug Components: Framework Reporter: Guillaume Nodet Assignee: Guillaume Nodet Priority: Minor I think there's a small possibility that an InvalidStateException is thrown when unregistering services after the bundle is stopped. It can only happen if the registration is held by someone and unregistered concurrently with the bundle being stopped. I think it does not hurt to catch and ignore it as I had it once. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira