Return-Path: 
 <issues-return-6341-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org>
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 698CB9A54
	for <apmail-karaf-issues-archive@minotaur.apache.org>;
 Wed, 11 Jan 2012 17:03:05 +0000 (UTC)
Received: (qmail 49172 invoked by uid 500); 11 Jan 2012 17:03:05 -0000
Delivered-To: apmail-karaf-issues-archive@karaf.apache.org
Received: (qmail 49123 invoked by uid 500); 11 Jan 2012 17:03:05 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 49035 invoked by uid 99); 11 Jan 2012 17:03:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2012 17:03:04 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2012 17:03:02 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 4CD7C145D59
	for <issues@karaf.apache.org>; Wed, 11 Jan 2012 17:02:41 +0000 (UTC)
Date: Wed, 11 Jan 2012 17:02:41 +0000 (UTC)
From: "Jamie goodyear (Closed) (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <1408419238.30491.1326301361316.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1962540997.18672.1297801557480.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (KARAF-464) JAAS service configuration tracker does
 not unregister services or respond to service updates
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/KARAF-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear closed KARAF-464.
--------------------------------

    
> JAAS service configuration tracker does not unregister services or respond to service updates
> ---------------------------------------------------------------------------------------------
>
>                 Key: KARAF-464
>                 URL: https://issues.apache.org/jira/browse/KARAF-464
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>            Reporter: Kurt Westerfeld
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.0
>
>
> The class org.apache.karaf.jaas.config.impl.OsgiConfiguration contains a java.util.List<JaasRealm> which is intended to track jaas realms added via blueprint via it's register/unregister pair using the whiteboard pattern.  This list is not mutated properly during unregister, since the list is not keyed by name or other id, and the passed in value during remove is a proxy.  Thus, after doing an "update" on a bundle that contains a jaas configuration, the list grows by one, but contains a stale service reference.
> When this occurs, a subsequent call to getAppConfigurationEntry() causes a runtime exception, "org.osgi.service.blueprint.container.ServiceUnavailableException".  No jaas-based authentication can happen after this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira