felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3915) [DS] Timing hole between ComponentHolder initial config and registration
Date Mon, 25 Feb 2013 04:40:13 GMT

    [ https://issues.apache.org/jira/browse/FELIX-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585619#comment-13585619

David Jencks commented on FELIX-3915:

Previous commit still has a timing hole, although it's small.  Patch has a way to use the
R5 getChangeCount to eliminate the hole, and uses pretty much the same idea as r 1449401 for
R4.  I can't find a R5 compendium in maven right now, so I'm using reflection.  Hoping to
improve things...
> [DS] Timing hole between ComponentHolder initial config and registration
> ------------------------------------------------------------------------
>                 Key: FELIX-3915
>                 URL: https://issues.apache.org/jira/browse/FELIX-3915
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.0
> Right now when we create a component holder we first try to configure it with any existing
configurations and then register it to obtain configuration events for it's pid.  Thus there
is a timing hole after the query for existing configurations and before the registration when
configuration events will be dropped.
> I'm doing the initial configuration after adding the holder to the by-pid map.  Instead
of missing the configuration entirely, it will be possible that the component would get configured
twice.  I don't think this can cause any harm.

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

View raw message