felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-550) SCR registers service component twice after stopping/starting a bundle
Date Mon, 02 Jun 2008 09:19:45 GMT

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

Carsten Ziegeler updated FELIX-550:

    Affects Version/s: scr-1.0.0
        Fix Version/s: scr-1.0.1

> SCR registers service component twice after stopping/starting a bundle
> ----------------------------------------------------------------------
>                 Key: FELIX-550
>                 URL: https://issues.apache.org/jira/browse/FELIX-550
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.0.0
>         Environment: JDK 1.6.0_03 / WinXP SP2
>            Reporter: Paul Neyens
>             Fix For: scr-1.0.1
> When stopping and starting a bundle (from the shell) that has a component which is also
registered as a service, this service is registered twice from time to time.
> What I am seeing, is that when starting the bundle (after stopping it first), the enable
method (AbstractComponentManager) is called starting an enableInternal' (including an activateInternal)
on the component actor thread.
> Approximately at the same time, an update call is made from the configuration manager
(on some thread from the CM, through method 'update' in ImmediateComponentManager's anonymous
ManagedService inner class) resulting eventually in a call to 'reactivate' which first deactivates
(deactivateInternal) on the current thread (CM thread). That's where things clash, I guess.
> I cannot reproduce this behaviour when logging level is set to debug.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message