[
https://issues.apache.org/jira/browse/KARAF-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995530#comment-12995530
]
Ioannis Canellos commented on KARAF-464:
----------------------------------------
I tried to reproduce the problem on trunk, by updating the bundle " Apache
Karaf :: JAAS" which contains the karaf jaas realm. As a result I noticed that
to the unregister method the actual object is passed and no proxy of it. So the
object was succesfully removed from the list and I couldn't reproduce this.
Did I lost something ? Could you please let us know on which version of karaf
you had this issue?
> 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: runtime
> Reporter: Kurt Westerfeld
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
