You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Jens Offenbach (JIRA)" <ji...@apache.org> on 2014/11/14 11:46:33 UTC

[jira] [Created] (FELIX-4698) SynchronousConfigurationListener

Jens Offenbach created FELIX-4698:
-------------------------------------

             Summary: SynchronousConfigurationListener
                 Key: FELIX-4698
                 URL: https://issues.apache.org/jira/browse/FELIX-4698
             Project: Felix
          Issue Type: Bug
          Components: Declarative Services (SCR)
    Affects Versions: scr-1.8.2
            Reporter: Jens Offenbach


When you directly create/update a configuration and delete it right after creation, the component instance creation of components which preconditions become fulfilled (using ConfigurationPolicy.REQUIRE) often fails. The reason is that events from the ConfigurationAdmin are delivered to SCR asynchronously. This results in the following behavior: SCR receives a configuration update event and accesses e.g. its properties. The call fails because the configuration was deleted in the meantime. A solution would be to implement  SynchronousConfigurationListener in the class CongurationSupport instead of ConfigurationListener. That forces the ConfigurationAdmin to deliver the update events before someone can delete the configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)